← previous blocknext block →recent activity
Analyzing
Block #92,223,538
22 transactions · 19 stateful · 2026-08-01 14:15:09 UTC
Parallelism
68/100
Blocked
42%
Avg conflicts / tx
0.77
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #92,223,538 · 22 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
1w02w13w05w27w18w39w410w515w619w020w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x19e1da6e…4a72
0x34b655…2a6f
8 touches
6 conflicts
0x4786839b…c29a
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…001f
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002f
0x1b6862…e19c
6 touches
3 conflicts
0x607e2ee6…759c
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x482471ad…122f
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
6 conflicts on slot 0x19e1da6e1d…454a72
Audit this contract →
← previous block·next block →recent activity