← previous blocknext block →recent activity
Analyzing
Block #83,633,218
12 transactions · 11 stateful · 2026-06-25 16:07:51 UTC
Parallelism
75/100
Blocked
27%
Avg conflicts / tx
0.5
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #83,633,218 · 12 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w05w18w211w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9ac79c76…c4a9
0x34b655…2a6f
6 touches
3 conflicts
0x0e8a204a…dd61
0x34b655…2a6f
4 touches
1 conflict
0x619f5683…5bd4
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x3ec82b22…1f46
0x34b655…2a6f
4 touches
1 conflict
0x6cd8284d…10eb
0x34b655…2a6f
2 touches
0 conflicts
0x8e5cc690…b06b
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
3 conflicts on slot 0x9ac79c76e2…88c4a9
Audit this contract →
← previous block·next block →recent activity