← previous blocknext block →recent activity
Analyzing
Block #92,407,666
20 transactions · 16 stateful · 2026-08-02 05:41:10 UTC
Parallelism
60/100
Blocked
50%
Avg conflicts / tx
0.85
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #92,407,666 · 20 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w16w27w39w411w513w216w617w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8f203394…f2db
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…641f
0x34b655…2a6f
8 touches
6 conflicts
0xc05d6eb3…9341
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…00c9
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xe561281f…7569
0x34b655…2a6f
8 touches
6 conflicts
0x12cae920…cbc9
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 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 0x8f2033941d…ebf2db
Audit this contract →
← previous block·next block →recent activity