← previous blocknext block →recent activity
Analyzing
Block #84,187,138
14 transactions · 10 stateful · 2026-06-28 05:40:22 UTC
Parallelism
79/100
Blocked
40%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #84,187,138 · 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
1w06w07w18w29w112w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa5f1d2ef…822e
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xda803d50…82c8
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x793aa64d…b09d
0x34b655…2a6f
4 touches
1 conflict
0xdfc5f346…7b42
0x40c49f…2af0
4 touches
1 conflict
0x00000000…001e
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…002e
0x1b6862…e19c
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 0xa5f1d2ef18…60822e
Audit this contract →
← previous block·next block →recent activity