← previous blocknext block →recent activity
Analyzing
Block #101,065,755
23 transactions · 21 stateful · 2026-09-01 14:27:09 UTC
Parallelism
74/100
Blocked
33%
Avg conflicts / tx
0.57
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #101,065,755 · 23 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w05w06w111w212w313w414w015w518w122w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4be9812b…48a9
0x34b655…2a6f
6 touches
3 conflicts
0x6f28b0ee…246c
0x34b655…2a6f
6 touches
3 conflicts
0x55192654…91fe
0x34b655…2a6f
6 touches
3 conflicts
0x7ea1cfdf…81c0
0xa6afd3…d132
4 touches
1 conflict
0x70e677f5…e3bd
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xbcdd58ff…0711
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 0x4be9812b87…d748a9
Audit this contract →
← previous block·next block →recent activity