← previous blocknext block →recent activity
Analyzing
Block #90,515,952
13 transactions · 11 stateful · 2026-07-26 15:01:50 UTC
Parallelism
85/100
Blocked
9%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,515,952 · 13 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x38badd90…a68c
0x34b655…2a6f
4 touches
1 conflict
0x555c6ba5…bf0a
0x34b655…2a6f
4 touches
1 conflict
0x0d488000…3831
0x34b655…2a6f
2 touches
0 conflicts
0x1683a436…2c42
0x34b655…2a6f
2 touches
0 conflicts
0x201679bc…0414
0x34b655…2a6f
2 touches
0 conflicts
0x20fbcaee…bb79
0x34b655…2a6f
2 touches
0 conflicts
0x4560e5a8…b741
0x34b655…2a6f
2 touches
0 conflicts
0x4a5956ef…e226
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0x38badd9042…8da68c
Audit this contract →
← previous block·next block →recent activity