← previous blocknext block →recent activity
Analyzing
Block #101,301,581
24 transactions · 22 stateful · 2026-09-02 10:13:49 UTC
Parallelism
71/100
Blocked
36%
Avg conflicts / tx
0.88
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #101,301,581 · 24 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w08w011w113w214w215w318w419w521w522w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x88e92ec7…696d
0x34b655…2a6f
10 touches
10 conflicts
0xb0650d8b…c70e
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…641f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x4e135144…4167
0x34b655…2a6f
6 touches
3 conflicts
0x0ed7cc0b…ee52
0x34b655…2a6f
6 touches
3 conflicts
0x5e782d17…5317
0x34b655…2a6f
6 touches
3 conflicts
0x640c4fb2…044a
0x34b655…2a6f
6 touches
3 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
10 conflicts on slot 0x88e92ec750…6f696d
Audit this contract →
← previous block·next block →recent activity