← previous blocknext block →recent activity
Analyzing
Block #101,091,447
23 transactions · 20 stateful · 2026-09-01 16:36:41 UTC
Parallelism
78/100
Blocked
25%
Avg conflicts / tx
0.35
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #101,091,447 · 23 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w15w06w210w218w322w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdcebb2b8…5f18
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x5cedd87b…8b81
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0xb3037bed…6b7c
0x34b655…2a6f
4 touches
1 conflict
0x7aad02c6…b979
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0028
0x1b6862…e19c
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
3 conflicts on slot 0xdcebb2b809…7d5f18
Audit this contract →
← previous block·next block →recent activity