← previous blocknext block →recent activity
Analyzing
Block #92,418,338
15 transactions · 15 stateful · 2026-08-02 06:34:50 UTC
Parallelism
80/100
Blocked
33%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #92,418,338 · 15 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w16w07w18w211w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7d9e2311…5f38
0x7b9256…1fb2
6 touches
3 conflicts
0x679a6fa2…44c4
0x7b9256…1fb2
6 touches
3 conflicts
0x7d9e2311…5f37
0x7b9256…1fb2
6 touches
3 conflicts
0x177211e2…1c2d
0x754704…b603
6 touches
3 conflicts
0xe1f61186…e2f8
0x754704…b603
6 touches
3 conflicts
0x00000000…0006
0x7b9256…1fb2
6 touches
3 conflicts
0x679a6fa2…44c0
0x7b9256…1fb2
6 touches
3 conflicts
0x679a6fa2…44c1
0x7b9256…1fb2
6 touches
3 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
3 conflicts on slot 0x7d9e2311eb…f25f38
Audit this contract →
← previous block·next block →recent activity