← previous blocknext block →recent activity
Analyzing
Block #92,188,917
18 transactions · 16 stateful · 2026-08-01 11:21:03 UTC
Parallelism
72/100
Blocked
63%
Avg conflicts / tx
1
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #92,188,917 · 18 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w06w17w28w39w010w111w212w313w416w117w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe01fcf41…45c3
0x7b9256…1fb2
8 touches
6 conflicts
0x177211e2…1c2d
0x754704…b603
8 touches
6 conflicts
0xe1f61186…e2f8
0x754704…b603
8 touches
6 conflicts
0x00000000…0006
0x7b9256…1fb2
8 touches
6 conflicts
0xaa060c3d…9ccc
0x7b9256…1fb2
8 touches
6 conflicts
0xaa060c3d…9ccd
0x7b9256…1fb2
8 touches
6 conflicts
0xaa060c3d…9cd0
0x7b9256…1fb2
8 touches
6 conflicts
0xe01fcf41…45c2
0x7b9256…1fb2
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: 0x7b9256fd…e21fb2
6 conflicts on slot 0xe01fcf413b…5845c3
Audit this contract →
← previous block·next block →recent activity