← previous blocknext block →recent activity
Analyzing
Block #83,658,841
13 transactions · 13 stateful · 2026-06-25 18:58:52 UTC
Parallelism
62/100
Blocked
31%
Avg conflicts / tx
0.62
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #83,658,841 · 13 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
2w03w14w27w38w011w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9863393c…ce7b
0x34b655…2a6f
8 touches
6 conflicts
0x022f72c3…07b6
0xc8689a…ee79
6 touches
3 conflicts
0x231930a8…6b87
0x34b655…2a6f
6 touches
3 conflicts
0x9e79fa16…b4c3
0x34b655…2a6f
6 touches
3 conflicts
0xd3d708df…612c
0x34b655…2a6f
6 touches
3 conflicts
0xe732567d…b65d
0x34b655…2a6f
6 touches
3 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
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
6 conflicts on slot 0x9863393ce4…4cce7b
Audit this contract →
← previous block·next block →recent activity