← previous blocknext block →recent activity
Analyzing
Block #83,653,881
22 transactions · 17 stateful · 2026-06-25 18:25:50 UTC
Parallelism
77/100
Blocked
35%
Avg conflicts / tx
0.41
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #83,653,881 · 22 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
5w07w18w29w316w017w118w220w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbd68c7c7…40b3
0x34b655…2a6f
6 touches
3 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
6 touches
3 conflicts
0x76477ddf…b8f8
0xc8689a…ee79
4 touches
1 conflict
0x6767aeb1…eabc
0x34b655…2a6f
4 touches
1 conflict
0x73ca2093…8dd6
0x34b655…2a6f
4 touches
1 conflict
0xc61310a5…949f
0x34b655…2a6f
4 touches
1 conflict
0xcb89a818…e7c1
0x34b655…2a6f
4 touches
1 conflict
0xf06c2cf5…61bd
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 0xbd68c7c758…bd40b3
Audit this contract →
← previous block·next block →recent activity