← previous blocknext block →recent activity
Analyzing
Block #101,325,781
36 transactions · 33 stateful · 2026-09-02 12:15:35 UTC
Parallelism
78/100
Blocked
61%
Avg conflicts / tx
1.14
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #101,325,781 · 36 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w15w26w07w08w09w111w112w213w314w416w218w320w426w529w130w131w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x544745e8…d72e
0x34b655…2a6f
10 touches
10 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x629e09e5…692a
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0x2a719b1d…365f
0x34b655…2a6f
6 touches
3 conflicts
0xe6126d77…a0ca
0x34b655…2a6f
6 touches
3 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
10 conflicts on slot 0x544745e82f…47d72e
Audit this contract →
← previous block·next block →recent activity