← previous blocknext block →recent activity
Analyzing
Block #90,782,834
14 transactions · 13 stateful · 2026-07-27 13:24:23 UTC
Parallelism
71/100
Blocked
31%
Avg conflicts / tx
0.57
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,782,834 · 14 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
3w05w06w07w18w29w310w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4a63d446…b00f
0x7b9256…1fb2
8 touches
6 conflicts
0x4a63d446…b00e
0x7b9256…1fb2
8 touches
6 conflicts
0xe1f61186…e2f8
0x754704…b603
8 touches
6 conflicts
0x177211e2…1c2d
0x754704…b603
8 touches
6 conflicts
0x01b037a0…466e
0x7b9256…1fb2
8 touches
6 conflicts
0x01b037a0…466d
0x7b9256…1fb2
8 touches
6 conflicts
0x4a63d446…b012
0x7b9256…1fb2
8 touches
6 conflicts
0x00000000…0006
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 0x4a63d446a2…14b00f
Audit this contract →
← previous block·next block →recent activity