← previous blocknext block →recent activity
Analyzing
Block #83,665,313
13 transactions · 12 stateful · 2026-06-25 19:41:57 UTC
Parallelism
54/100
Blocked
50%
Avg conflicts / tx
1.23
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #83,665,313 · 13 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w25w37w49w011w412w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x85b992ec…db0e
0x34b655…2a6f
8 touches
6 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
8 touches
6 conflicts
0x022f72c3…07b6
0xc8689a…ee79
6 touches
3 conflicts
0x06571461…d6f0
0x34b655…2a6f
6 touches
3 conflicts
0x157dbfb2…4089
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x6b47245e…a342
0x34b655…2a6f
6 touches
3 conflicts
0x7e859bb7…f7e0
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
6 conflicts on slot 0x85b992ec49…95db0e
Audit this contract →
← previous block·next block →recent activity