← previous blocknext block →recent activity
Analyzing
Block #95,161,823
26 transactions · 23 stateful · 2026-08-11 20:53:47 UTC
Parallelism
73/100
Blocked
52%
Avg conflicts / tx
1.19
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #95,161,823 · 26 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w36w07w48w111w012w113w214w215w316w419w524w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x660dab48…6990
0x34b655…2a6f
12 touches
15 conflicts
0xbe9baf16…df37
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xec7d120d…7084
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0002
0xeae24c…0be0
6 touches
3 conflicts
0x90a021f0…f922
0x34b655…2a6f
6 touches
3 conflicts
0x2029b74e…c206
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
15 conflicts on slot 0x660dab48d8…526990
Audit this contract →
← previous block·next block →recent activity