← previous blocknext block →recent activity
Analyzing
Block #90,274,356
18 transactions · 17 stateful · 2026-07-25 18:31:58 UTC
Parallelism
72/100
Blocked
41%
Avg conflicts / tx
0.72
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #90,274,356 · 18 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
1w02w13w24w06w17w08w110w211w316w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x96c6ca66…371b
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0xab0760c4…4cfd
0x34b655…2a6f
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x0d488000…3831
0x34b655…2a6f
6 touches
3 conflicts
0x910a6959…34b7
0x34b655…2a6f
4 touches
1 conflict
0x935a37fd…0514
0x34b655…2a6f
4 touches
1 conflict
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
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 0x96c6ca6629…17371b
Audit this contract →
← previous block·next block →recent activity