← previous blocknext block →recent activity
Analyzing
Block #92,319,081
14 transactions · 14 stateful · 2026-08-01 22:15:42 UTC
Parallelism
64/100
Blocked
36%
Avg conflicts / tx
0.79
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #92,319,081 · 14 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
1w03w14w05w16w27w38w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb02eac4f…b327
0x7b9256…1fb2
10 touches
10 conflicts
0x177211e2…1c2d
0x754704…b603
10 touches
10 conflicts
0xe1f61186…e2f8
0x754704…b603
10 touches
10 conflicts
0x00000000…0006
0x7b9256…1fb2
10 touches
10 conflicts
0x632b783e…f553
0x7b9256…1fb2
10 touches
10 conflicts
0x632b783e…f554
0x7b9256…1fb2
10 touches
10 conflicts
0x632b783e…f557
0x7b9256…1fb2
10 touches
10 conflicts
0xb02eac4f…b326
0x7b9256…1fb2
10 touches
10 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
10 conflicts on slot 0xb02eac4fea…39b327
Audit this contract →
← previous block·next block →recent activity