← previous blocknext block →recent activity
Analyzing
Block #90,045,527
14 transactions · 14 stateful · 2026-07-24 23:15:38 UTC
Parallelism
64/100
Blocked
57%
Avg conflicts / tx
1.07
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #90,045,527 · 14 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w26w07w18w29w310w411w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0005
0x370e2e…63b4
10 touches
10 conflicts
0x55b4e430…44cb
0x754704…b603
10 touches
10 conflicts
0x00000000…0006
0x0a2fbf…29b1
10 touches
10 conflicts
0x2106a309…1698
0x0a2fbf…29b1
10 touches
10 conflicts
0x2106a309…1699
0x0a2fbf…29b1
10 touches
10 conflicts
0x2106a309…169c
0x0a2fbf…29b1
10 touches
10 conflicts
0x8e254b43…2075
0x0a2fbf…29b1
10 touches
10 conflicts
0x8e254b43…2076
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: 0x370e2ee6…bd63b4
10 conflicts on slot 0x0000000000…000005
Audit this contract →
← previous block·next block →recent activity