← previous blocknext block →recent activity
Analyzing
Block #101,325,616
24 transactions · 19 stateful · 2026-09-02 12:14:45 UTC
Parallelism
71/100
Blocked
32%
Avg conflicts / tx
0.5
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #101,325,616 · 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
3w04w15w06w27w317w019w421w523w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0xbb975a6c…bff4
0x34b655…2a6f
6 touches
3 conflicts
0x629e09e5…692a
0x34b655…2a6f
6 touches
3 conflicts
0xbc8fb280…76a3
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xf95f86cd…e927
0x34b655…2a6f
4 touches
1 conflict
0x45bbf84b…5e85
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 0xac2a02739b…81721b
Audit this contract →
← previous block·next block →recent activity