← previous blocknext block →recent activity
Analyzing
Block #83,660,816
14 transactions · 12 stateful · 2026-06-25 19:12:00 UTC
Parallelism
57/100
Blocked
42%
Avg conflicts / tx
0.71
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #83,660,816 · 14 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w15w26w310w411w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x46d5a052…ff2e
0x34b655…2a6f
6 touches
3 conflicts
0xbd68c7c7…40b3
0x34b655…2a6f
6 touches
3 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
6 touches
3 conflicts
0x454d8940…cfe7
0x34b655…2a6f
4 touches
1 conflict
0x55384053…4a1f
0x34b655…2a6f
4 touches
1 conflict
0x89d753fb…f258
0x34b655…2a6f
4 touches
1 conflict
0x97d5efed…1aa4
0x34b655…2a6f
4 touches
1 conflict
0x9b58e20f…2dd9
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
3 conflicts on slot 0x46d5a0529d…adff2e
Audit this contract →
← previous block·next block →recent activity