← previous blocknext block →recent activity

Analyzing

Block #75,552,063

15 transactions · 13 stateful · 2026-05-19 05:43:46 UTC

Parallelism

80/100

Blocked

38%

Avg conflicts / tx

0.67

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #75,552,063  ·  15 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others

Conflict graph

Blocked by

- write/write- - read/write

x = tx position · y = wave (depth)

Hot storage slots

Contention

0x908d4442…2c4b

0x34b655…2a6f

6 touches
3 conflicts

0xf0a7ca33…3c7e

0x34b655…2a6f

6 touches
3 conflicts

0xe54a1f6f…18f2

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xef97c27b…a280

0xd32edf…ff58

5 touches
3 conflicts

0x0711ec2d…d973

0x34b655…2a6f

4 touches
1 conflict

0x313f2565…5b00

0x34b655…2a6f

4 touches
1 conflict

0x57de3828…3fbb

0x34b655…2a6f

4 touches
1 conflict

What's blocking what?

Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.

The bottleneck

Throughput-killer: 0x34b6552d…112a6f

3 conflicts on slot 0x908d4442aa…222c4b

← previous block·next block →recent activity