← previous blocknext block →recent activity
Analyzing
Block #90,795,463
68 transactions · 60 stateful · 2026-07-27 14:27:57 UTC
Parallelism
69/100
Blocked
80%
Avg conflicts / tx
3.47
Longest chain
21 deep
Execution timeline
did this block parallelize well?
view
block #90,795,463 · 68 txs across 21 waves · depth 21
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
wave w17
wave w18
wave w19
wave w20
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w07w18w29w310w411w512w613w714w815w941w1042w145w1149w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
24 touches
66 conflicts
0x889d5e90…929a
0x2a68ba…90c5
22 touches
55 conflicts
0x449d101e…ea3f
0xa6afd3…d132
20 touches
45 conflicts
0x00000000…003d
0xa6afd3…d132
20 touches
45 conflicts
0x0fffa5c0…a3a9
0xa6afd3…d132
18 touches
36 conflicts
0xdb067026…9eb8
0x2b46c0…1669
16 touches
28 conflicts
0x5778d110…d2e6
0xc8689a…ee79
16 touches
28 conflicts
0xd6bd849a…5597
0x2a68ba…90c5
16 touches
28 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: Perpl
66 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity