← previous blocknext block →recent activity
Analyzing
Block #101,500,814
13 transactions · 9 stateful · 2026-09-03 02:56:21 UTC
Parallelism
77/100
Blocked
22%
Avg conflicts / tx
0.15
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #101,500,814 · 13 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
2w03w19w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfd713bab…a651
0x34b655…2a6f
4 touches
1 conflict
0x9c088939…ddd7
0x34b655…2a6f
4 touches
1 conflict
0xa77312ea…f240
0x34b655…2a6f
4 touches
1 conflict
0xaaf36ccb…f35c
0x34b655…2a6f
4 touches
1 conflict
0xb58ed141…c32e
0x34b655…2a6f
4 touches
1 conflict
0xb70f92cf…da8b
0x34b655…2a6f
4 touches
1 conflict
0xc52785b9…08f8
0x34b655…2a6f
4 touches
1 conflict
0xda50c9d5…674e
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 0xfd713bab1a…98a651
Audit this contract →
← previous block·next block →recent activity