← previous blocknext block →recent activity
Analyzing
Block #90,795,843
20 transactions · 20 stateful · 2026-07-27 14:29:52 UTC
Parallelism
75/100
Blocked
55%
Avg conflicts / tx
1.15
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #90,795,843 · 20 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w06w07w18w210w312w213w114w215w316w317w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1691317e…7f1e
0x34b655…2a6f
10 touches
10 conflicts
0x889d5e90…929a
0x2a68ba…90c5
8 touches
6 conflicts
0x731f2745…9370
0xa6afd3…d132
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0xfb31d278…9107
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x0fffa5c0…a3a9
0xa6afd3…d132
6 touches
3 conflicts
0x8c8774b6…40b9
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
10 conflicts on slot 0x1691317e73…957f1e
Audit this contract →
← previous block·next block →recent activity