← previous blocknext block →recent activity
Analyzing
Block #92,333,118
14 transactions · 14 stateful · 2026-08-01 23:26:17 UTC
Parallelism
50/100
Blocked
50%
Avg conflicts / tx
1.57
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #92,333,118 · 14 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
3w04w05w16w27w38w49w510w611w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xeafa0c90…ae63
0x7b9256…1fb2
14 touches
21 conflicts
0xff26b5f6…6a26
0x7b9256…1fb2
14 touches
21 conflicts
0xff26b5f6…6a27
0x7b9256…1fb2
14 touches
21 conflicts
0x00000000…0006
0x7b9256…1fb2
14 touches
21 conflicts
0xeafa0c90…ae5f
0x7b9256…1fb2
14 touches
21 conflicts
0xeafa0c90…ae60
0x7b9256…1fb2
14 touches
21 conflicts
0x177211e2…1c2d
0x754704…b603
14 touches
21 conflicts
0xe1f61186…e2f8
0x754704…b603
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 0xeafa0c900a…35ae63
Audit this contract →
← previous block·next block →recent activity