← previous blocknext block →recent activity
Analyzing
Block #90,787,296
20 transactions · 19 stateful · 2026-07-27 13:46:50 UTC
Parallelism
85/100
Blocked
37%
Avg conflicts / tx
0.35
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,787,296 · 20 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w14w08w011w112w113w114w215w016w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x91803cbc…2f15
0x34b655…2a6f
4 touches
1 conflict
0x538f77c2…a9e7
0xa6afd3…d132
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0xc5d7e85d…b578
0x40c49f…2af0
4 touches
1 conflict
0xfcc8f826…7c5f
0x34b655…2a6f
4 touches
1 conflict
0xda27c764…7fab
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
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
1 conflict on slot 0x91803cbc00…8c2f15
Audit this contract →
← previous block·next block →recent activity