← previous blocknext block →recent activity
Analyzing
Block #92,080,335
16 transactions · 15 stateful · 2026-08-01 02:14:58 UTC
Parallelism
63/100
Blocked
60%
Avg conflicts / tx
1.56
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #92,080,335 · 16 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w26w38w09w110w411w212w313w414w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6ee54916…c118
0x7b9256…1fb2
12 touches
15 conflicts
0x6ee54916…c119
0x7b9256…1fb2
12 touches
15 conflicts
0xa6505a46…08a4
0x7b9256…1fb2
12 touches
15 conflicts
0xa6505a46…08a5
0x7b9256…1fb2
12 touches
15 conflicts
0xa6505a46…08a8
0x7b9256…1fb2
12 touches
15 conflicts
0x177211e2…1c2d
0x754704…b603
12 touches
15 conflicts
0xe1f61186…e2f8
0x754704…b603
12 touches
15 conflicts
0x00000000…0006
0x7b9256…1fb2
12 touches
15 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
15 conflicts on slot 0x6ee5491662…93c118
Audit this contract →
← previous block·next block →recent activity