← previous blocknext block →recent activity
Analyzing
Block #92,173,800
16 transactions · 16 stateful · 2026-08-01 10:05:03 UTC
Parallelism
63/100
Blocked
38%
Avg conflicts / tx
1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #92,173,800 · 16 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
2w03w14w05w18w29w310w412w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…00c9
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…641f
0x34b655…2a6f
12 touches
15 conflicts
0x80398c66…f3cc
0x34b655…2a6f
10 touches
10 conflicts
0x87ab06cc…147e
0x34b655…2a6f
8 touches
6 conflicts
0x2cf02ca9…f960
0x34b655…2a6f
8 touches
6 conflicts
0xc13e1d5c…62c6
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xdab87f9b…3a80
0x34b655…2a6f
7 touches
6 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 0x0000000000…0000c9
Audit this contract →
← previous block·next block →recent activity