← previous blocknext block →recent activity
Analyzing
Block #101,017,061
9 transactions · 9 stateful · 2026-09-01 10:22:06 UTC
Parallelism
78/100
Blocked
11%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #101,017,061 · 9 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
5w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x689f8625…e470
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x295bd070…34a3
0x34b655…2a6f
4 touches
1 conflict
0x4f2778a8…8415
0x34b655…2a6f
4 touches
1 conflict
0x2f4f4437…1d3e
0x34b655…2a6f
2 touches
0 conflicts
0x41c56387…a8f6
0x34b655…2a6f
2 touches
0 conflicts
0x5209e6a8…bb9a
0x34b655…2a6f
2 touches
0 conflicts
0x551735ee…6ece
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 0x689f8625f1…cce470
Audit this contract →
← previous block·next block →recent activity