← previous blocknext block →recent activity
Analyzing
Block #92,300,872
12 transactions · 11 stateful · 2026-08-01 20:44:07 UTC
Parallelism
83/100
Blocked
9%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #92,300,872 · 12 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x68caa37b…c795
0x34b655…2a6f
4 touches
1 conflict
0x5cc477b5…1cf3
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x889d5e90…929a
0x2a68ba…90c5
2 touches
0 conflicts
0x0a762f71…f1c8
0x34b655…2a6f
2 touches
0 conflicts
0x0bd1061b…6f3f
0x34b655…2a6f
2 touches
0 conflicts
0x1486184c…f1ae
0x34b655…2a6f
2 touches
0 conflicts
0x1f81f132…f9b5
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0x68caa37b30…f7c795
Audit this contract →
← previous block·next block →recent activity