← previous blocknext block →recent activity
Analyzing
Block #84,512,846
24 transactions · 18 stateful · 2026-06-29 17:51:26 UTC
Parallelism
75/100
Blocked
50%
Avg conflicts / tx
0.54
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #84,512,846 · 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
1w02w112w013w114w215w316w318w119w222w423w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
8 touches
6 conflicts
0x178fe051…465a
0x34b655…2a6f
4 touches
1 conflict
0x3766925b…76fe
0x34b655…2a6f
4 touches
1 conflict
0x3da49e5d…8067
0x34b655…2a6f
4 touches
1 conflict
0x49b0842d…0a93
0x34b655…2a6f
4 touches
1 conflict
0x4c4d720f…3b1b
0x34b655…2a6f
4 touches
1 conflict
0x5db49f05…91a6
0x34b655…2a6f
4 touches
1 conflict
0x89ef0dba…31e2
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
6 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity