← previous blocknext block →recent activity
Analyzing
Block #101,955,840
13 transactions · 13 stateful · 2026-09-04 17:08:01 UTC
Parallelism
85/100
Blocked
15%
Avg conflicts / tx
0.23
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #101,955,840 · 13 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
1w03w07w011w112w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0x58620f29…db5a
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xf690d06e…5e46
0x34b655…2a6f
4 touches
1 conflict
0xffdc4ab0…9626
0x34b655…2a6f
4 touches
1 conflict
0x0755c2d7…d723
0x34b655…2a6f
2 touches
0 conflicts
0x1e7cd294…034b
0x34b655…2a6f
2 touches
0 conflicts
0x2a3f40b6…e39c
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 0x51fc8795c8…57126f
Audit this contract →
← previous block·next block →recent activity