← previous blocknext block →recent activity
Analyzing
Block #84,005,470
10 transactions · 8 stateful · 2026-06-27 09:30:34 UTC
Parallelism
80/100
Blocked
13%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,005,470 · 10 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
2w03w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb5637b01…c1c5
0x34b655…2a6f
4 touches
1 conflict
0x3da49e5d…8067
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x18978822…2623
0x34b655…2a6f
2 touches
0 conflicts
0x2c4b1b8e…8392
0x34b655…2a6f
2 touches
0 conflicts
0x5ae3ff69…5845
0x34b655…2a6f
2 touches
0 conflicts
0x60e18dd0…25f1
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 0xb5637b012f…88c1c5
Audit this contract →
← previous block·next block →recent activity