← previous blocknext block →recent activity
Analyzing
Block #101,323,565
29 transactions · 21 stateful · 2026-09-02 12:04:26 UTC
Parallelism
90/100
Blocked
33%
Avg conflicts / tx
0.34
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #101,323,565 · 29 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
1w04w05w110w011w113w022w123w224w125w228w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc2fe3907…bd7b
0x34b655…2a6f
6 touches
3 conflicts
0x5095cb33…2491
0xa6afd3…d132
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x6bd3cf7e…f835
0x40c49f…2af0
4 touches
1 conflict
0x10a5a231…be40
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
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
3 conflicts on slot 0xc2fe39078e…4bbd7b
Audit this contract →
← previous block·next block →recent activity