← previous blocknext block →recent activity
Analyzing
Block #83,639,108
14 transactions · 13 stateful · 2026-06-25 16:47:11 UTC
Parallelism
79/100
Blocked
31%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #83,639,108 · 14 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
3w04w17w08w111w112w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0a8f8b9c…3046
0x34b655…2a6f
4 touches
1 conflict
0x235dd62b…f416
0x34b655…2a6f
4 touches
1 conflict
0x3e2c3d66…b580
0x34b655…2a6f
4 touches
1 conflict
0x408e66bb…3d6b
0x34b655…2a6f
4 touches
1 conflict
0x5aed1bd2…7afa
0x34b655…2a6f
4 touches
1 conflict
0x62d6e82b…a750
0x34b655…2a6f
4 touches
1 conflict
0x78ae5f62…86ea
0x34b655…2a6f
4 touches
1 conflict
0x7b6d2deb…dde0
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
1 conflict on slot 0x0a8f8b9c32…e53046
Audit this contract →
← previous block·next block →recent activity