← previous blocknext block →recent activity
Analyzing
Block #92,176,214
19 transactions · 18 stateful · 2026-08-01 10:17:11 UTC
Parallelism
63/100
Blocked
61%
Avg conflicts / tx
1.63
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #92,176,214 · 19 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w16w27w28w39w410w511w616w317w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf54ec28e…d70f
0x7b9256…1fb2
14 touches
21 conflicts
0x00000000…0006
0x7b9256…1fb2
14 touches
21 conflicts
0xe1f61186…e2f8
0x754704…b603
14 touches
21 conflicts
0x177211e2…1c2d
0x754704…b603
14 touches
21 conflicts
0xf54ec28e…d70c
0x7b9256…1fb2
14 touches
21 conflicts
0xf54ec28e…d70b
0x7b9256…1fb2
14 touches
21 conflicts
0x5752ce4a…e76d
0x7b9256…1fb2
14 touches
21 conflicts
0x5752ce4a…e76c
0x7b9256…1fb2
14 touches
21 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
21 conflicts on slot 0xf54ec28e91…e7d70f
Audit this contract →
← previous block·next block →recent activity