← previous blocknext block →recent activity
Analyzing
Block #90,220,611
19 transactions · 18 stateful · 2026-07-25 14:01:01 UTC
Parallelism
68/100
Blocked
50%
Avg conflicts / tx
1.32
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #90,220,611 · 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
1w02w13w26w39w010w311w412w514w015w216w317w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xda27c764…7fab
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x64275949…d698
0x34b655…2a6f
6 touches
3 conflicts
0x172b0de5…980b
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x74362807…e577
0x34b655…2a6f
6 touches
3 conflicts
0x15437606…7ec7
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
6 conflicts on slot 0xda27c76455…2e7fab
Audit this contract →
← previous block·next block →recent activity