← previous blocknext block →recent activity
Analyzing
Block #90,036,095
13 transactions · 13 stateful · 2026-07-24 22:28:04 UTC
Parallelism
85/100
Blocked
23%
Avg conflicts / tx
0.38
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,036,095 · 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
1w02w13w05w06w07w111w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf7f78508…6b24
0x34b655…2a6f
4 touches
1 conflict
0x0cab691e…74a5
0x34b655…2a6f
4 touches
1 conflict
0x1ab04d57…b60b
0x34b655…2a6f
4 touches
1 conflict
0x31ec17e3…8912
0x34b655…2a6f
4 touches
1 conflict
0x31ec17e3…8913
0x34b655…2a6f
4 touches
1 conflict
0xaae6463e…bfcc
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
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 0xf7f7850884…ab6b24
Audit this contract →
← previous block·next block →recent activity