← previous blocknext block →recent activity
Analyzing
Block #101,658,953
13 transactions · 13 stateful · 2026-09-03 16:11:53 UTC
Parallelism
77/100
Blocked
31%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #101,658,953 · 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
1w02w13w04w15w29w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8385f5fe…9552
0x34b655…2a6f
6 touches
3 conflicts
0xaaf36ccb…f35c
0x34b655…2a6f
6 touches
3 conflicts
0xc0d89cb0…184b
0x34b655…2a6f
6 touches
3 conflicts
0x230b0b56…a675
0x34b655…2a6f
6 touches
3 conflicts
0xda50c9d5…674e
0x34b655…2a6f
6 touches
3 conflicts
0x8bf661cb…bcd2
0x34b655…2a6f
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x0b3a121c…f803
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 0x8385f5febe…919552
Audit this contract →
← previous block·next block →recent activity