← previous blocknext block →recent activity
Analyzing
Block #90,602,757
42 transactions · 39 stateful · 2026-07-26 22:18:29 UTC
Parallelism
62/100
Blocked
64%
Avg conflicts / tx
2.07
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #90,602,757 · 42 txs across 16 waves · depth 16
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w07w08w19w010w011w112w213w314w415w518w123w924w1026w129w230w133w1136w1239w15
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0a57a2b8…3cdd
0x34b655…2a6f
14 touches
21 conflicts
0xf2f4727d…cdb7
0x34b655…2a6f
12 touches
15 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xf18906a6…d2e3
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xfc3d5171…8357
0x34b655…2a6f
8 touches
6 conflicts
0xb519996d…4224
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
21 conflicts on slot 0x0a57a2b8cd…773cdd
Audit this contract →
← previous block·next block →recent activity