← previous blocknext block →recent activity
Analyzing
Block #90,530,159
13 transactions · 13 stateful · 2026-07-26 16:13:18 UTC
Parallelism
69/100
Blocked
38%
Avg conflicts / tx
0.62
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,530,159 · 13 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
3w04w15w26w38w09w110w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x439cfb2c…7b9e
0xa6afd3…d132
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0x89678d1b…463e
0xa6afd3…d132
4 touches
1 conflict
0xffe2ad64…fd9f
0xa6afd3…d132
3 touches
1 conflict
0xa81d958c…46bf
0xa6afd3…d132
3 touches
1 conflict
0x88403d65…91a5
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
6 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity