← previous blocknext block →recent activity
Analyzing
Block #90,544,364
9 transactions · 9 stateful · 2026-07-26 17:24:45 UTC
Parallelism
67/100
Blocked
22%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,544,364 · 9 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
2w06w17w2
- 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
0xd5d0b681…ca6c
0x34b655…2a6f
4 touches
1 conflict
0xdc208608…f600
0x34b655…2a6f
4 touches
1 conflict
0x0ec7fb56…bca1
0x34b655…2a6f
2 touches
0 conflicts
0x2c8f52ce…fe9a
0x34b655…2a6f
2 touches
0 conflicts
0x34d95d94…3a16
0x34b655…2a6f
2 touches
0 conflicts
0x38d7a7f4…ffe6
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