← previous blocknext block →recent activity
Analyzing
Block #90,036,604
10 transactions · 9 stateful · 2026-07-24 22:30:38 UTC
Parallelism
70/100
Blocked
22%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,036,604 · 10 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
3w04w05w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x45ea7a97…bbb3
0x34b655…2a6f
4 touches
1 conflict
0xdc57bb0d…6fa9
0x34b655…2a6f
4 touches
1 conflict
0x4aaa2679…4c1d
0x34b655…2a6f
4 touches
1 conflict
0x12bdece2…85bc
0x34b655…2a6f
2 touches
0 conflicts
0x1507536e…933f
0x34b655…2a6f
2 touches
0 conflicts
0x52b467b5…4fbc
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
3 conflicts on slot 0xbcbf5d09a8…c68bac
Audit this contract →
← previous block·next block →recent activity