← previous blocknext block →recent activity
Analyzing
Block #101,309,258
31 transactions · 23 stateful · 2026-09-02 10:52:27 UTC
Parallelism
84/100
Blocked
52%
Avg conflicts / tx
0.77
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #101,309,258 · 31 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
2w03w06w18w210w011w113w114w215w116w224w325w326w429w330w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x49339736…b223
0x34b655…2a6f
10 touches
10 conflicts
0xaad6be10…0801
0x2a68ba…90c5
8 touches
6 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0xed903df2…6ea4
0x34b655…2a6f
4 touches
1 conflict
0x91ca1434…4017
0x34b655…2a6f
4 touches
1 conflict
0xb5cddf91…0abf
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
10 conflicts on slot 0x4933973697…38b223
Audit this contract →
← previous block·next block →recent activity