← previous blocknext block →recent activity
Analyzing
Block #101,305,662
25 transactions · 18 stateful · 2026-09-02 10:34:21 UTC
Parallelism
84/100
Blocked
28%
Avg conflicts / tx
0.36
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #101,305,662 · 25 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
1w02w15w06w17w016w217w320w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbc2de485…918d
0x34b655…2a6f
6 touches
3 conflicts
0xe3c95990…b264
0x34b655…2a6f
6 touches
3 conflicts
0x97b04948…c8e7
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xe3f405ac…d620
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xdfa159d0…1576
0x065c9d…c394
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 0xbc2de48528…c6918d
Audit this contract →
← previous block·next block →recent activity