← previous blocknext block →recent activity
Analyzing
Block #101,662,713
24 transactions · 23 stateful · 2026-09-03 16:30:48 UTC
Parallelism
75/100
Blocked
43%
Avg conflicts / tx
0.58
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #101,662,713 · 24 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
1w02w13w24w06w38w49w010w113w414w118w220w522w023w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x024b482b…16b0
0x34b655…2a6f
6 touches
3 conflicts
0x1a2e73cf…5ff5
0x34b655…2a6f
6 touches
3 conflicts
0x8bf661cb…bcd2
0x34b655…2a6f
6 touches
3 conflicts
0x987859be…2686
0x34b655…2a6f
6 touches
3 conflicts
0xb40e601f…bf98
0x34b655…2a6f
6 touches
3 conflicts
0xb826ef15…d248
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xd98afa6e…3364
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
3 conflicts on slot 0x024b482b0a…2616b0
Audit this contract →
← previous block·next block →recent activity