← previous blocknext block →recent activity
Analyzing
Block #92,079,949
16 transactions · 16 stateful · 2026-08-01 02:13:01 UTC
Parallelism
63/100
Blocked
44%
Avg conflicts / tx
1.06
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #92,079,949 · 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
4w05w06w17w28w39w410w511w114w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa4484db3…0de2
0x7b9256…1fb2
12 touches
15 conflicts
0xc0e71bb2…202e
0x7b9256…1fb2
12 touches
15 conflicts
0x00000000…0006
0x7b9256…1fb2
12 touches
15 conflicts
0xa4484db3…0dde
0x7b9256…1fb2
12 touches
15 conflicts
0xa4484db3…0ddf
0x7b9256…1fb2
12 touches
15 conflicts
0xc0e71bb2…202d
0x7b9256…1fb2
12 touches
15 conflicts
0x177211e2…1c2d
0x754704…b603
12 touches
15 conflicts
0xe1f61186…e2f8
0x754704…b603
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 0xa4484db323…ae0de2
Audit this contract →
← previous block·next block →recent activity