← previous blocknext block →recent activity
Analyzing
Block #92,767,496
19 transactions · 17 stateful · 2026-08-03 11:52:09 UTC
Parallelism
58/100
Blocked
41%
Avg conflicts / tx
1.16
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #92,767,496 · 19 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
1w02w13w25w08w39w410w511w613w7
- 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
10 touches
10 conflicts
0xfcfb570f…cf1c
0x34b655…2a6f
10 touches
10 conflicts
0x0b35df1d…7c83
0x34b655…2a6f
8 touches
6 conflicts
0xea6c2d78…6ac9
0x34b655…2a6f
8 touches
6 conflicts
0x48a29a03…c437
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x5b3f9959…fede
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 0x0000000000…0000c9
Audit this contract →
← previous block·next block →recent activity