← previous blocknext block →recent activity
Analyzing
Block #90,626,330
14 transactions · 14 stateful · 2026-07-27 00:17:05 UTC
Parallelism
64/100
Blocked
43%
Avg conflicts / tx
0.86
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #90,626,330 · 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
1w02w13w04w17w28w310w412w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x71af6501…8eba
0x34b655…2a6f
8 touches
6 conflicts
0xcf6c1a79…b07f
0x34b655…2a6f
8 touches
6 conflicts
0x1b25f260…c429
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…00c9
0x34b655…2a6f
8 touches
6 conflicts
0x3bdd71a2…b6eb
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…641f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 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
6 conflicts on slot 0x71af6501af…e68eba
Audit this contract →
← previous block·next block →recent activity