← previous blocknext block →recent activity
Analyzing
Block #83,634,321
21 transactions · 18 stateful · 2026-06-25 16:15:13 UTC
Parallelism
67/100
Blocked
50%
Avg conflicts / tx
1
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #83,634,321 · 21 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
1w02w14w07w08w19w210w312w114w015w416w118w519w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x610aa855…5ecd
0x34b655…2a6f
10 touches
10 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
10 touches
10 conflicts
0x022f72c3…07b6
0xc8689a…ee79
8 touches
6 conflicts
0x157dbfb2…4089
0x34b655…2a6f
8 touches
6 conflicts
0x8e5cc690…b06b
0x34b655…2a6f
8 touches
6 conflicts
0x9fbabe09…8dd6
0x34b655…2a6f
8 touches
6 conflicts
0xa50f5e4b…d9cb
0x34b655…2a6f
8 touches
6 conflicts
0xe64e6363…e676
0x34b655…2a6f
8 touches
6 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
10 conflicts on slot 0x610aa855f6…ba5ecd
Audit this contract →
← previous block·next block →recent activity