← previous blocknext block →recent activity
Analyzing
Block #92,691,864
20 transactions · 19 stateful · 2026-08-03 05:31:26 UTC
Parallelism
70/100
Blocked
37%
Avg conflicts / tx
0.9
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #92,691,864 · 20 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w210w011w112w213w314w415w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x44ad89ba…cf83
0xe4f6e7…9657
12 touches
15 conflicts
0x724cd9ff…6684
0x0cc9b2…7777
12 touches
15 conflicts
0x00000000…0008
0x0ea966…0742
12 touches
15 conflicts
0x724cd9ff…6684
0xe4f6e7…9657
12 touches
15 conflicts
0x00000000…0018
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0028
0x1b6862…e19c
6 touches
3 conflicts
0x64e1f0ce…7156
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
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: 0xe4f6e757…919657
15 conflicts on slot 0x44ad89ba62…49cf83
Audit this contract →
← previous block·next block →recent activity