← previous blocknext block →recent activity
Analyzing
Block #89,745,959
13 transactions · 12 stateful · 2026-07-23 22:06:17 UTC
Parallelism
69/100
Blocked
50%
Avg conflicts / tx
0.69
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #89,745,959 · 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
1w02w13w05w06w17w28w19w310w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x090a0b40…f1f0
0x0a2fbf…29b1
8 touches
6 conflicts
0x55b4e430…44cb
0x754704…b603
8 touches
6 conflicts
0x00000000…0006
0x0a2fbf…29b1
8 touches
6 conflicts
0x090a0b40…f1ec
0x0a2fbf…29b1
8 touches
6 conflicts
0x090a0b40…f1ed
0x0a2fbf…29b1
8 touches
6 conflicts
0xd397d119…96f0
0x370e2e…63b4
6 touches
3 conflicts
0xb9405511…a403
0x0a2fbf…29b1
6 touches
3 conflicts
0xb9405511…a404
0x0a2fbf…29b1
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: 0x0a2fbf2d…f729b1
6 conflicts on slot 0x090a0b4072…96f1f0
Audit this contract →
← previous block·next block →recent activity