← previous blocknext block →recent activity
Analyzing
Block #90,890,460
76 transactions · 58 stateful · 2026-07-27 22:25:58 UTC
Parallelism
78/100
Blocked
81%
Avg conflicts / tx
2.93
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #90,890,460 · 76 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
1w02w03w14w213w015w316w120w121w223w325w426w528w653w756w459w563w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x48cba2…b48b
24 touches
66 conflicts
0x889d5e90…929a
0x2a68ba…90c5
16 touches
28 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
16 touches
28 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
12 touches
15 conflicts
0x76d1e78d…7877
0x40c49f…2af0
12 touches
15 conflicts
0x00000000…003d
0x40c49f…2af0
12 touches
15 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: 0x48cba278…e2b48b
66 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity