← previous blocknext block →recent activity
Analyzing
Block #92,789,067
18 transactions · 17 stateful · 2026-08-03 13:40:41 UTC
Parallelism
67/100
Blocked
41%
Avg conflicts / tx
1.17
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #92,789,067 · 18 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w36w07w18w49w510w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x56153262…21ce
0x34b655…2a6f
12 touches
15 conflicts
0xd66696e0…0842
0x34b655…2a6f
12 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0x948836ff…59ab
0x34b655…2a6f
6 touches
4 conflicts
0xd1b40f29…9b9d
0x34b655…2a6f
6 touches
3 conflicts
0xcfae7788…fec8
0x34b655…2a6f
5 touches
3 conflicts
0xa20c3eed…7612
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
15 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity