← previous blocknext block →recent activity
Analyzing
Block #84,335,020
41 transactions · 26 stateful · 2026-06-28 22:05:43 UTC
Parallelism
83/100
Blocked
62%
Avg conflicts / tx
1.07
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #84,335,020 · 41 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w16w18w216w017w118w219w320w421w522w628w230w331w239w440w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
14 touches
21 conflicts
0x4bdcc5ee…7e90
0x34b655…2a6f
10 touches
10 conflicts
0xe02484a6…c32e
0xc8689a…ee79
8 touches
6 conflicts
0x75194ada…a1c5
0x34b655…2a6f
8 touches
6 conflicts
0x7cb2f3fa…4836
0x34b655…2a6f
8 touches
6 conflicts
0x8e739938…e7ab
0x34b655…2a6f
8 touches
6 conflicts
0x968b8c05…a0fb
0x34b655…2a6f
6 touches
3 conflicts
0x0833f1ab…71e7
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
21 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity