← previous blocknext block →recent activity
Analyzing
Block #84,493,861
27 transactions · 23 stateful · 2026-06-29 15:44:44 UTC
Parallelism
70/100
Blocked
57%
Avg conflicts / tx
0.85
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #84,493,861 · 27 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w17w210w011w112w213w315w416w018w219w220w323w524w625w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbc9aaf19…8cfd
0x34b655…2a6f
8 touches
6 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
8 touches
6 conflicts
0x31aa2853…8dbb
0xc8689a…ee79
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x83f3d320…fb59
0x34b655…2a6f
6 touches
3 conflicts
0x9af72ba2…f151
0x34b655…2a6f
6 touches
3 conflicts
0xb6836671…5c3c
0x34b655…2a6f
6 touches
3 conflicts
0xc94da5de…7ca7
0x34b655…2a6f
6 touches
3 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
6 conflicts on slot 0xbc9aaf1962…178cfd
Audit this contract →
← previous block·next block →recent activity