← previous blocknext block →recent activity
Analyzing
Block #90,301,240
19 transactions · 18 stateful · 2026-07-25 20:48:37 UTC
Parallelism
68/100
Blocked
50%
Avg conflicts / tx
1.11
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #90,301,240 · 19 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
1w02w13w05w06w17w28w39w411w512w216w017w118w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x14716474…0666
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…00c9
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0xa065de59…3f32
0x34b655…2a6f
6 touches
3 conflicts
0xa46242d8…c0a7
0x34b655…2a6f
6 touches
3 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 0x147164744f…2f0666
Audit this contract →
← previous block·next block →recent activity