← previous blocknext block →recent activity
Analyzing
Block #76,261,846
13 transactions · 12 stateful · 2026-05-22 12:34:12 UTC
Parallelism
85/100
Blocked
17%
Avg conflicts / tx
0.15
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #76,261,846 · 13 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w08w111w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3347cbe5…846c
0x34b655…2a6f
4 touches
1 conflict
0xd5bfc8fb…071f
0x2a68ba…90c5
4 touches
1 conflict
0x11560115…bfc2
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x3a6e7600…e1f1
0xa6afd3…d132
4 touches
1 conflict
0xdb9d8189…e926
0xa6afd3…d132
4 touches
1 conflict
0x38e2407a…b4d3
0xa6afd3…d132
3 touches
1 conflict
0x1775cf2c…6b6d
0x6a7e3f…292d
2 touches
0 conflicts
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: Perpl
1 conflict on slot 0x3347cbe5ae…92846c
Audit this contract →
← previous block·next block →recent activity