← previous blocknext block →recent activity
Analyzing
Block #90,958,201
12 transactions · 11 stateful · 2026-07-28 04:06:44 UTC
Parallelism
50/100
Blocked
45%
Avg conflicts / tx
0.5
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #90,958,201 · 12 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w36w48w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2e641595…ce8d
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x520f8a31…65c5
0x34b655…2a6f
4 touches
1 conflict
0x520f8a31…65c6
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x93ffcd76…894e
0x34b655…2a6f
4 touches
1 conflict
0x957c875f…b3f9
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 0x2e6415951b…36ce8d
Audit this contract →
← previous block·next block →recent activity