← previous blocknext block →recent activity
Analyzing
Block #101,300,492
18 transactions · 17 stateful · 2026-09-02 10:08:20 UTC
Parallelism
83/100
Blocked
29%
Avg conflicts / tx
0.44
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #101,300,492 · 18 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
1w05w07w18w011w113w214w117w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x676207a8…5d7e
0x34b655…2a6f
6 touches
3 conflicts
0x8571fbdb…345a
0x34b655…2a6f
6 touches
3 conflicts
0x48c32766…2afc
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xe9695c7f…fbff
0x34b655…2a6f
4 touches
1 conflict
0xec1d6663…6042
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
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 0x676207a88a…e05d7e
Audit this contract →
← previous block·next block →recent activity