← previous blocknext block →recent activity
Analyzing
Block #101,095,947
13 transactions · 12 stateful · 2026-09-01 16:59:19 UTC
Parallelism
77/100
Blocked
25%
Avg conflicts / tx
0.23
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #101,095,947 · 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
6w07w111w212w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdcebb2b8…5f18
0x34b655…2a6f
4 touches
1 conflict
0x711e4ba1…40ee
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
2 touches
0 conflicts
0xb87af72a…aef6
0x2a68ba…90c5
2 touches
0 conflicts
0x48ed1159…abe9
0x34ae4d…3fc5
2 touches
0 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
1 conflict on slot 0xdcebb2b809…7d5f18
Audit this contract →
← previous block·next block →recent activity