← previous blocknext block →recent activity
Analyzing
Block #92,443,451
24 transactions · 20 stateful · 2026-08-02 08:41:07 UTC
Parallelism
63/100
Blocked
50%
Avg conflicts / tx
0.88
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #92,443,451 · 24 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w26w37w18w49w518w619w721w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa69a8250…d650
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x2385516f…eca5
0x34b655…2a6f
8 touches
6 conflicts
0xd66696e0…0842
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x6f900be0…cd6e
0x34b655…2a6f
6 touches
3 conflicts
0x6e6b8ec7…2197
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
10 conflicts on slot 0xa69a82501a…94d650
Audit this contract →
← previous block·next block →recent activity