← previous blocknext block →recent activity
Analyzing
Block #101,092,310
22 transactions · 21 stateful · 2026-09-01 16:41:01 UTC
Parallelism
77/100
Blocked
29%
Avg conflicts / tx
0.32
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #101,092,310 · 22 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w05w06w19w113w214w315w417w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x627738d1…db02
0x34b655…2a6f
6 touches
3 conflicts
0xcf37f77e…a027
0x34b655…2a6f
4 touches
1 conflict
0xe1a004ad…c2bc
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x02a46223…6845
0x34b655…2a6f
4 touches
1 conflict
0x1d351a9b…f2dd
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
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 0x627738d150…b6db02
Audit this contract →
← previous block·next block →recent activity