← previous blocknext block →recent activity
Analyzing
Block #92,237,960
16 transactions · 15 stateful · 2026-08-01 15:27:41 UTC
Parallelism
75/100
Blocked
47%
Avg conflicts / tx
0.75
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #92,237,960 · 16 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
2w03w14w25w06w17w28w310w011w112w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9c77a2af…4b6e
0x7b9256…1fb2
8 touches
6 conflicts
0x9c77a2af…4b6b
0x7b9256…1fb2
8 touches
6 conflicts
0x9c77a2af…4b6a
0x7b9256…1fb2
8 touches
6 conflicts
0x177211e2…1c2d
0x754704…b603
8 touches
6 conflicts
0xe1f61186…e2f8
0x754704…b603
8 touches
6 conflicts
0x00000000…0006
0x7b9256…1fb2
8 touches
6 conflicts
0xd710c18f…f455
0x7b9256…1fb2
8 touches
6 conflicts
0xd710c18f…f454
0x7b9256…1fb2
8 touches
6 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
6 conflicts on slot 0x9c77a2af21…804b6e
Audit this contract →
← previous block·next block →recent activity