← previous blocknext block →recent activity
Analyzing
Block #83,633,910
14 transactions · 13 stateful · 2026-06-25 16:12:29 UTC
Parallelism
86/100
Blocked
15%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #83,633,910 · 14 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w18w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xafd867b7…2b2d
0x34b655…2a6f
4 touches
1 conflict
0xafd867b7…2b2e
0x34b655…2a6f
4 touches
1 conflict
0xb3975d93…b4a2
0x34b655…2a6f
4 touches
1 conflict
0x5d4a3441…e31c
0x34b655…2a6f
4 touches
1 conflict
0x275f56fe…dcfb
0x34b655…2a6f
3 touches
1 conflict
0x86263271…c1f0
0x34b655…2a6f
3 touches
1 conflict
0x590d5781…40c7
0x40c49f…2af0
2 touches
0 conflicts
0x90917d58…114d
0x40c49f…2af0
2 touches
0 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
1 conflict on slot 0xafd867b7ed…d92b2d
Audit this contract →
← previous block·next block →recent activity