← previous blocknext block →recent activity
Analyzing
Block #90,028,416
17 transactions · 17 stateful · 2026-07-24 21:49:26 UTC
Parallelism
59/100
Blocked
47%
Avg conflicts / tx
1.24
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #90,028,416 · 17 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
2w05w06w19w210w111w312w413w214w516w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x45ea7a97…bbb3
0x34b655…2a6f
12 touches
15 conflicts
0x8eef368f…aa21
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xc5031114…58ac
0x34b655…2a6f
6 touches
3 conflicts
0x6ec32eb4…697e
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x43fab434…896f
0xa6afd3…d132
6 touches
3 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
15 conflicts on slot 0x45ea7a9723…bdbbb3
Audit this contract →
← previous block·next block →recent activity