← previous blocknext block →recent activity
Analyzing
Block #92,349,064
10 transactions · 9 stateful · 2026-08-02 00:46:28 UTC
Parallelism
60/100
Blocked
44%
Avg conflicts / tx
0.6
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #92,349,064 · 10 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
2w03w15w27w38w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca608d0c…f23b
0x34b655…2a6f
6 touches
3 conflicts
0x15f0d0cb…f404
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xc2fd8d22…e676
0x34b655…2a6f
4 touches
1 conflict
0x4147b177…c9ba
0x34b655…2a6f
4 touches
1 conflict
0x56153262…21ce
0x34b655…2a6f
4 touches
1 conflict
0x69656781…3c53
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
3 conflicts on slot 0xca608d0ccc…6ff23b
Audit this contract →
← previous block·next block →recent activity