← previous blocknext block →recent activity
Analyzing
Block #84,573,954
24 transactions · 20 stateful · 2026-06-30 00:39:22 UTC
Parallelism
75/100
Blocked
35%
Avg conflicts / tx
0.58
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #84,573,954 · 24 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w016w118w219w320w422w523w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x2f7781d6…e632
0x34b655…2a6f
6 touches
3 conflicts
0x97d5efed…1aa4
0x34b655…2a6f
6 touches
3 conflicts
0xf98f45fd…37b1
0x34b655…2a6f
6 touches
3 conflicts
0x7585925a…3f45
0x34b655…2a6f
5 touches
3 conflicts
0x3149127f…19a9
0x34b655…2a6f
4 touches
1 conflict
0x5d32a251…d929
0x34b655…2a6f
4 touches
1 conflict
0x6bafad69…617b
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: Perpl
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity