← previous blocknext block →recent activity
Analyzing
Block #101,501,241
13 transactions · 12 stateful · 2026-09-03 02:58:30 UTC
Parallelism
69/100
Blocked
25%
Avg conflicts / tx
0.54
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #101,501,241 · 13 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w211w012w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xee89bdca…6046
0x34b655…2a6f
6 touches
3 conflicts
0x8bf661cb…bcd2
0x34b655…2a6f
6 touches
3 conflicts
0xdaa21e16…8342
0x34b655…2a6f
6 touches
3 conflicts
0x8b113392…6b42
0x34b655…2a6f
6 touches
3 conflicts
0xfd713bab…a651
0x34b655…2a6f
6 touches
3 conflicts
0x9c088939…ddd7
0x34b655…2a6f
6 touches
3 conflicts
0x9bff3222…a246
0x34b655…2a6f
5 touches
3 conflicts
0xb75367ff…a2b7
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 0xee89bdca32…426046
Audit this contract →
← previous block·next block →recent activity