← previous blocknext block →recent activity
Analyzing
Block #90,893,373
74 transactions · 62 stateful · 2026-07-27 22:40:38 UTC
Parallelism
73/100
Blocked
81%
Avg conflicts / tx
3.18
Longest chain
20 deep
Execution timeline
did this block parallelize well?
view
block #90,893,373 · 74 txs across 20 waves · depth 20
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w47w48w515w316w417w520w623w726w827w957w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x48cba2…b48b
20 touches
45 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
20 touches
45 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
18 touches
36 conflicts
0x889d5e90…929a
0x2a68ba…90c5
16 touches
28 conflicts
0x92385428…6941
0x34b655…2a6f
14 touches
21 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
14 touches
21 conflicts
0x27db07af…a7b4
0xd32edf…ff58
11 touches
15 conflicts
0x4c188934…158e
0x34b655…2a6f
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: 0x48cba278…e2b48b
45 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity