← previous blocknext block →recent activity
Analyzing
Block #84,545,124
14 transactions · 13 stateful · 2026-06-29 21:26:55 UTC
Parallelism
86/100
Blocked
23%
Avg conflicts / tx
0.21
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,545,124 · 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
1w05w06w07w18w19w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x99246de6…5bd5
0x34b655…2a6f
4 touches
1 conflict
0xebcc54b0…d437
0x34b655…2a6f
4 touches
1 conflict
0xd3e7b883…08fe
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x07c7dce7…e2b3
0xd32edf…ff58
3 touches
1 conflict
0x793aa64d…b09d
0x34b655…2a6f
2 touches
0 conflicts
0x793aa64d…b09c
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 0x99246de64f…485bd5
Audit this contract →
← previous block·next block →recent activity