← previous blocknext block →recent activity
Analyzing
Block #83,653,092
9 transactions · 7 stateful · 2026-06-25 18:20:35 UTC
Parallelism
78/100
Blocked
29%
Avg conflicts / tx
0.33
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #83,653,092 · 9 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
1w02w03w18w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf324b405…ca30
0x34b655…2a6f
4 touches
1 conflict
0x16588efe…2a3c
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x4467ecee…e95b
0x34b655…2a6f
4 touches
1 conflict
0x47a43ab9…4f8a
0x34b655…2a6f
4 touches
1 conflict
0xd2453506…54e4
0x34b655…2a6f
4 touches
1 conflict
0xe99d8e68…a16e
0x34b655…2a6f
4 touches
1 conflict
0x26f451fc…4466
0x34b655…2a6f
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 0xf324b40549…56ca30
Audit this contract →
← previous block·next block →recent activity