← previous blocknext block →recent activity
Analyzing
Block #90,393,962
16 transactions · 15 stateful · 2026-07-26 04:42:47 UTC
Parallelism
63/100
Blocked
47%
Avg conflicts / tx
1.06
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #90,393,962 · 16 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w07w18w29w310w411w514w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…641f
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…00c9
0x34b655…2a6f
12 touches
15 conflicts
0x72da4494…8b2f
0x34b655…2a6f
10 touches
10 conflicts
0x1c097b81…0164
0x34b655…2a6f
10 touches
10 conflicts
0xd8a62cfe…b68a
0x34b655…2a6f
9 touches
10 conflicts
0x8f888556…f387
0x34b655…2a6f
9 touches
10 conflicts
0xd6d040d9…9ae3
0x34b655…2a6f
8 touches
6 conflicts
0xe3280296…788e
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
15 conflicts on slot 0xc824469a90…af641f
Audit this contract →
← previous block·next block →recent activity