← previous blocknext block →recent activity
Analyzing
Block #90,945,554
40 transactions · 35 stateful · 2026-07-28 03:03:07 UTC
Parallelism
80/100
Blocked
74%
Avg conflicts / tx
1.85
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #90,945,554 · 40 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w36w17w28w311w412w013w129w330w531w632w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x48cba2…b48b
16 touches
28 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…003d
0xa6afd3…d132
10 touches
10 conflicts
0x889d5e90…929a
0x2a68ba…90c5
10 touches
10 conflicts
0x3464bbc5…a323
0xa6afd3…d132
10 touches
10 conflicts
0x1803586e…d149
0xa6afd3…d132
10 touches
10 conflicts
0xf219f7cf…7379
0xa6afd3…d132
8 touches
6 conflicts
0xbe0001df…bdad
0xd32edf…ff58
7 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: 0x48cba278…e2b48b
28 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity