← previous blocknext block →recent activity
Analyzing
Block #92,692,716
16 transactions · 15 stateful · 2026-08-03 05:35:44 UTC
Parallelism
50/100
Blocked
60%
Avg conflicts / tx
1.88
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #92,692,716 · 16 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
1w02w13w04w15w26w37w49w510w613w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xda46a376…f6a6
0x34b655…2a6f
16 touches
28 conflicts
0xc824469a…6425
0x34b655…2a6f
16 touches
28 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xd66696e0…0842
0x34b655…2a6f
10 touches
10 conflicts
0x53103bb4…02a1
0x34b655…2a6f
6 touches
3 conflicts
0x7bbff01b…62a6
0x34b655…2a6f
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x2d071de0…c86e
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
28 conflicts on slot 0xda46a376d7…59f6a6
Audit this contract →
← previous block·next block →recent activity