← previous blocknext block →recent activity
Analyzing
Block #83,616,211
39 transactions · 33 stateful · 2026-06-25 14:14:10 UTC
Parallelism
67/100
Blocked
58%
Avg conflicts / tx
1.72
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #83,616,211 · 39 txs across 13 waves · depth 13
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w05w16w07w08w09w111w216w017w118w219w320w421w522w623w724w825w326w435w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
18 touches
36 conflicts
0x1e346a85…e9c5
0x34b655…2a6f
12 touches
15 conflicts
0x2484cc15…5afc
0x34b655…2a6f
8 touches
6 conflicts
0xe02484a6…c32e
0xc8689a…ee79
8 touches
6 conflicts
0x5941ac48…c525
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x5a5dd7b4…fba4
0x34b655…2a6f
6 touches
3 conflicts
0xd06d821c…e5d0
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
36 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity