← previous blocknext block →recent activity
Analyzing
Block #92,079,449
16 transactions · 15 stateful · 2026-08-01 02:10:30 UTC
Parallelism
50/100
Blocked
67%
Avg conflicts / tx
2.06
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #92,079,449 · 16 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w06w17w28w39w410w511w612w713w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x69b5aab5…d56c
0x7b9256…1fb2
16 touches
28 conflicts
0x69b5aab5…d56b
0x7b9256…1fb2
16 touches
28 conflicts
0x177211e2…1c2d
0x754704…b603
16 touches
28 conflicts
0xe1f61186…e2f8
0x754704…b603
16 touches
28 conflicts
0x00000000…0006
0x7b9256…1fb2
16 touches
28 conflicts
0xe8c1c05a…b2ca
0x7b9256…1fb2
16 touches
28 conflicts
0xe8c1c05a…b2cb
0x7b9256…1fb2
16 touches
28 conflicts
0xe8c1c05a…b2ce
0x7b9256…1fb2
16 touches
28 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
28 conflicts on slot 0x69b5aab5bf…82d56c
Audit this contract →
← previous block·next block →recent activity