← previous blocknext block →recent activity
Analyzing
Block #90,231,017
15 transactions · 12 stateful · 2026-07-25 14:53:31 UTC
Parallelism
67/100
Blocked
50%
Avg conflicts / tx
0.6
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #90,231,017 · 15 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w07w19w212w314w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0aa5e418…5d1d
0x34b655…2a6f
6 touches
3 conflicts
0xcc58c80b…ff79
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x4ca37118…3c71
0x34b655…2a6f
4 touches
1 conflict
0x9a3068dd…18f1
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
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 0x0aa5e41824…be5d1d
Audit this contract →
← previous block·next block →recent activity