← previous blocknext block →recent activity
Analyzing
Block #92,012,728
11 transactions · 11 stateful · 2026-07-31 20:34:56 UTC
Parallelism
64/100
Blocked
36%
Avg conflicts / tx
0.82
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #92,012,728 · 11 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w27w39w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x67708716…f9b6
0x34b655…2a6f
8 touches
6 conflicts
0xcef70a96…db44
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xd8e7cb6f…2717
0x34b655…2a6f
4 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x56a284d9…32e4
0x34b655…2a6f
4 touches
1 conflict
0x79e8f935…c3b6
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 0x67708716f8…89f9b6
Audit this contract →
← previous block·next block →recent activity