← previous blocknext block →recent activity
Analyzing
Block #92,650,343
12 transactions · 10 stateful · 2026-08-03 02:01:44 UTC
Parallelism
83/100
Blocked
10%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #92,650,343 · 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
7w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7da56943…9753
0x34b655…2a6f
4 touches
1 conflict
0xb3c96942…f0fc
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xdadee63d…484c
0x34b655…2a6f
4 touches
1 conflict
0x1bd69a6a…2b8a
0x34b655…2a6f
3 touches
1 conflict
0x11de3a6d…2740
0x447d2e…e9f5
2 touches
0 conflicts
0x13cf84c6…2602
0x447d2e…e9f5
2 touches
0 conflicts
0x3e758e25…ec08
0x447d2e…e9f5
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 0x7da56943bc…d89753
Audit this contract →
← previous block·next block →recent activity