← previous blocknext block →recent activity
Analyzing
Block #89,677,408
20 transactions · 19 stateful · 2026-07-23 16:20:19 UTC
Parallelism
80/100
Blocked
47%
Avg conflicts / tx
0.8
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #89,677,408 · 20 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
1w02w13w05w17w28w010w111w012w113w214w315w318w019w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0006
0x0a2fbf…29b1
8 touches
6 conflicts
0x99c527d4…26c2
0x0a2fbf…29b1
8 touches
6 conflicts
0x99c527d4…26c3
0x0a2fbf…29b1
8 touches
6 conflicts
0x99c527d4…26c6
0x0a2fbf…29b1
8 touches
6 conflicts
0xc42435cd…0ce0
0x0a2fbf…29b1
8 touches
6 conflicts
0xc42435cd…0ce1
0x0a2fbf…29b1
8 touches
6 conflicts
0x00000000…0005
0x370e2e…63b4
8 touches
6 conflicts
0x1bff683e…7ecb
0x754704…b603
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: 0x0a2fbf2d…f729b1
6 conflicts on slot 0x0000000000…000006
Audit this contract →
← previous block·next block →recent activity