← previous blocknext block →recent activity
Analyzing
Block #90,834,692
26 transactions · 22 stateful · 2026-07-27 17:45:24 UTC
Parallelism
85/100
Blocked
41%
Avg conflicts / tx
0.46
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,834,692 · 26 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w09w012w113w114w215w217w218w324w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2c23489e…a0da
0x34b655…2a6f
6 touches
3 conflicts
0xfb31d278…9107
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x0fffa5c0…a3a9
0xa6afd3…d132
4 touches
1 conflict
0x0ad1fc8b…7516
0x34b655…2a6f
4 touches
1 conflict
0x9b2d3bee…8eeb
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 0x2c23489ef4…a0a0da
Audit this contract →
← previous block·next block →recent activity