← previous blocknext block →recent activity
Analyzing
Block #90,959,695
20 transactions · 17 stateful · 2026-07-28 04:14:14 UTC
Parallelism
65/100
Blocked
41%
Avg conflicts / tx
1.1
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #90,959,695 · 20 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w111w012w113w214w315w416w517w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x705ab4ae…0162
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0xbde524f4…43bf
0x34b655…2a6f
14 touches
21 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
14 touches
21 conflicts
0xcacd7c8e…1c55
0x34b655…2a6f
8 touches
6 conflicts
0x8fb4eb03…d211
0x34b655…2a6f
5 touches
3 conflicts
0xbf7bff89…1c5a
0x34b655…2a6f
5 touches
3 conflicts
0xc824469a…641e
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
21 conflicts on slot 0x705ab4ae45…c40162
Audit this contract →
← previous block·next block →recent activity