← previous blocknext block →recent activity
Analyzing
Block #101,955,364
10 transactions · 8 stateful · 2026-09-04 17:05:37 UTC
Parallelism
70/100
Blocked
38%
Avg conflicts / tx
0.3
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #101,955,364 · 10 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
2w03w15w07w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfcd7574f…a3a2
0x34b655…2a6f
4 touches
1 conflict
0xb3e293fe…be2e
0x34b655…2a6f
4 touches
1 conflict
0xb75367ff…a2b7
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xf5d28bce…c32c
0x34b655…2a6f
4 touches
1 conflict
0x024b482b…16b0
0x34b655…2a6f
4 touches
1 conflict
0x1a2e73cf…5ff5
0x34b655…2a6f
4 touches
1 conflict
0x29a58269…011a
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
1 conflict on slot 0xfcd7574f97…54a3a2
Audit this contract →
← previous block·next block →recent activity