← previous blocknext block →recent activity
Analyzing
Block #90,722,559
16 transactions · 15 stateful · 2026-07-27 08:21:11 UTC
Parallelism
63/100
Blocked
60%
Avg conflicts / tx
0.88
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #90,722,559 · 16 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
1w02w13w24w05w16w28w310w311w314w415w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9ca52d19…da85
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x0e91dab0…e1b2
0xa6afd3…d132
6 touches
3 conflicts
0xb2022d4d…0ca0
0xa6afd3…d132
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0xdb067026…9eb8
0x2b46c0…1669
4 touches
1 conflict
0x100f5e80…0ab2
0x34b655…2a6f
4 touches
1 conflict
0x110a671c…e284
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 0x9ca52d19e1…69da85
Audit this contract →
← previous block·next block →recent activity