← previous blocknext block →recent activity
Analyzing
Block #82,733,931
25 transactions · 18 stateful · 2026-06-21 11:59:35 UTC
Parallelism
80/100
Blocked
44%
Avg conflicts / tx
0.52
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #82,733,931 · 25 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w26w07w18w29w310w217w324w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x77d4ad2d…583c
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x08913286…f0df
0x34b655…2a6f
6 touches
3 conflicts
0x803beb89…d606
0xa6afd3…d132
6 touches
3 conflicts
0x23a320fb…cbd7
0x34b655…2a6f
4 touches
1 conflict
0x337583a8…b943
0x34b655…2a6f
4 touches
1 conflict
0x45ea7a97…bbb3
0x34b655…2a6f
4 touches
1 conflict
0x4f4bdabd…ffba
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
3 conflicts on slot 0x77d4ad2df0…97583c
Audit this contract →
← previous block·next block →recent activity