← previous blocknext block →recent activity
Analyzing
Block #90,220,854
11 transactions · 11 stateful · 2026-07-25 14:02:14 UTC
Parallelism
73/100
Blocked
27%
Avg conflicts / tx
0.45
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,220,854 · 11 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
2w04w05w17w08w210w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8f791153…4f53
0x34b655…2a6f
4 touches
1 conflict
0x95504918…3623
0x34b655…2a6f
4 touches
1 conflict
0xaea2f389…0305
0x34b655…2a6f
4 touches
1 conflict
0xc4998e49…c79d
0x34b655…2a6f
4 touches
1 conflict
0xebac0f82…a49c
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x3270d9f8…099a
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 0x8f7911535b…524f53
Audit this contract →
← previous block·next block →recent activity