← previous blocknext block →recent activity
Analyzing
Block #90,224,719
28 transactions · 27 stateful · 2026-07-25 14:21:45 UTC
Parallelism
39/100
Blocked
67%
Avg conflicts / tx
4.93
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #90,224,719 · 28 txs across 17 waves · depth 17
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
wave w15
wave w16
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w07w18w29w310w411w512w613w714w815w917w1018w1119w1220w1321w1422w1523w1624w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0006
0x0a2fbf…29b1
34 touches
136 conflicts
0x00000000…0005
0x370e2e…63b4
34 touches
136 conflicts
0x1bff683e…7ecb
0x754704…b603
34 touches
136 conflicts
0x55b4e430…44cb
0x754704…b603
34 touches
136 conflicts
0x6e72a4a7…3618
0x0a2fbf…29b1
24 touches
66 conflicts
0x6e72a4a7…361b
0x0a2fbf…29b1
24 touches
66 conflicts
0x0053fc0f…e62f
0x0a2fbf…29b1
24 touches
66 conflicts
0x0053fc0f…e62e
0x0a2fbf…29b1
24 touches
66 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
136 conflicts on slot 0x0000000000…000006
Audit this contract →
← previous block·next block →recent activity