← previous blocknext block →recent activity
Analyzing
Block #100,749,144
26 transactions · 22 stateful · 2026-08-31 11:53:55 UTC
Parallelism
85/100
Blocked
32%
Avg conflicts / tx
0.46
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,749,144 · 26 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w26w07w111w013w114w215w322w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x937a52a8…2719
0x34b655…2a6f
8 touches
6 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0x55192654…91fe
0x34b655…2a6f
6 touches
3 conflicts
0x1a3d2527…8ca0
0x34b655…2a6f
4 touches
1 conflict
0x28eed2ad…c4b2
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xc10b903d…2f54
0x34b655…2a6f
4 touches
1 conflict
0xca608d0c…f23b
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
6 conflicts on slot 0x937a52a895…d12719
Audit this contract →
← previous block·next block →recent activity