← previous blocknext block →recent activity
Analyzing
Block #83,635,334
34 transactions · 29 stateful · 2026-06-25 16:22:00 UTC
Parallelism
56/100
Blocked
69%
Avg conflicts / tx
2.71
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #83,635,334 · 34 txs across 15 waves · depth 15
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
wave w13
wave w14
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w16w27w39w410w512w013w116w017w118w219w320w421w522w623w724w825w926w1027w1130w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
24 touches
66 conflicts
0xd3d708df…612c
0x34b655…2a6f
12 touches
15 conflicts
0x022f72c3…07b6
0xc8689a…ee79
12 touches
15 conflicts
0x9fbabe09…8dd6
0x34b655…2a6f
12 touches
15 conflicts
0xe732567d…b65d
0x34b655…2a6f
12 touches
15 conflicts
0x8e5cc690…b06b
0x34b655…2a6f
12 touches
15 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
12 touches
15 conflicts
0x2f7f1a44…eeeb
0x34b655…2a6f
11 touches
15 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
66 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity