← previous blocknext block →recent activity
Analyzing
Block #92,287,041
10 transactions · 9 stateful · 2026-08-01 19:34:33 UTC
Parallelism
70/100
Blocked
22%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #92,287,041 · 10 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x18978822…2623
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0x6c28863e…840e
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…641f
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…00c9
0x34b655…2a6f
6 touches
3 conflicts
0xcf2db8f6…ca36
0x34b655…2a6f
5 touches
3 conflicts
0x46ee3c65…4ab8
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…642d
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 0x18978822b6…2c2623
Audit this contract →
← previous block·next block →recent activity