← previous blocknext block →recent activity
Analyzing
Block #90,116,670
18 transactions · 17 stateful · 2026-07-25 05:16:57 UTC
Parallelism
67/100
Blocked
47%
Avg conflicts / tx
1.17
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #90,116,670 · 18 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w27w08w19w210w311w412w514w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0006
0x0a2fbf…29b1
12 touches
15 conflicts
0x2e2998c5…9028
0x0a2fbf…29b1
12 touches
15 conflicts
0x2e2998c5…9025
0x0a2fbf…29b1
12 touches
15 conflicts
0x55b4e430…44cb
0x754704…b603
12 touches
15 conflicts
0x2e2998c5…9024
0x0a2fbf…29b1
12 touches
15 conflicts
0x00000000…0005
0x370e2e…63b4
10 touches
10 conflicts
0xa30a222d…4a92
0x0a2fbf…29b1
10 touches
10 conflicts
0xa30a222d…4a91
0x0a2fbf…29b1
10 touches
10 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
15 conflicts on slot 0x0000000000…000006
Audit this contract →
← previous block·next block →recent activity