← previous blocknext block →recent activity
Analyzing
Block #90,225,493
25 transactions · 24 stateful · 2026-07-25 14:25:39 UTC
Parallelism
40/100
Blocked
67%
Avg conflicts / tx
4.32
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #90,225,493 · 25 txs across 15 waves · depth 15
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w06w17w28w39w410w511w612w713w814w915w1016w1117w1218w1319w1420w121w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0006
0x0a2fbf…29b1
30 touches
105 conflicts
0x7850a7e0…0e14
0x0a2fbf…29b1
30 touches
105 conflicts
0x7850a7e0…0e15
0x0a2fbf…29b1
30 touches
105 conflicts
0x7850a7e0…0e18
0x0a2fbf…29b1
30 touches
105 conflicts
0x7850a7e0…0e1a
0x0a2fbf…29b1
30 touches
105 conflicts
0x00000000…0005
0x370e2e…63b4
30 touches
105 conflicts
0x1bff683e…7ecb
0x754704…b603
30 touches
105 conflicts
0x55b4e430…44cb
0x754704…b603
30 touches
105 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
105 conflicts on slot 0x0000000000…000006
Audit this contract →
← previous block·next block →recent activity