← previous blocknext block →recent activity
Analyzing
Block #90,629,694
20 transactions · 20 stateful · 2026-07-27 00:34:01 UTC
Parallelism
80/100
Blocked
25%
Avg conflicts / tx
0.35
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,629,694 · 20 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w06w17w08w19w214w118w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x217bd767…b79e
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x80fc7c2a…b248
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x8a705be8…7ac4
0xc8689a…ee79
4 touches
1 conflict
0x3347cbe5…846c
0x34b655…2a6f
4 touches
1 conflict
0x4f412a3d…b1f7
0x34b655…2a6f
4 touches
1 conflict
0xc2019d5b…0332
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
3 conflicts on slot 0x217bd767aa…4fb79e
Audit this contract →
← previous block·next block →recent activity