← previous blocknext block →recent activity
Analyzing
Block #92,221,671
13 transactions · 13 stateful · 2026-08-01 14:05:46 UTC
Parallelism
69/100
Blocked
38%
Avg conflicts / tx
0.69
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #92,221,671 · 13 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w06w17w28w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x38fe2630…f3e9
0x7b9256…1fb2
6 touches
3 conflicts
0x915eb02e…5cfe
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
0x38fe2630…f3e8
0x7b9256…1fb2
6 touches
3 conflicts
0x915eb02e…5cfb
0x7b9256…1fb2
6 touches
3 conflicts
0x915eb02e…5cfa
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 0x38fe263027…f0f3e9
Audit this contract →
← previous block·next block →recent activity