← previous blocknext block →recent activity
Analyzing
Block #92,342,281
12 transactions · 11 stateful · 2026-08-02 00:12:22 UTC
Parallelism
42/100
Blocked
73%
Avg conflicts / tx
1.33
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #92,342,281 · 12 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w36w37w49w410w511w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x90d75b1f…1664
0x34b655…2a6f
8 touches
6 conflicts
0x4ff5ffda…05aa
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xbb84f537…c9b2
0x34b655…2a6f
6 touches
3 conflicts
0x202125c4…e4cc
0xd32edf…ff58
5 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x0132f71c…5643
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
6 conflicts on slot 0x90d75b1f3e…4c1664
Audit this contract →
← previous block·next block →recent activity