← previous blocknext block →recent activity
Analyzing
Block #90,602,931
18 transactions · 17 stateful · 2026-07-26 22:19:22 UTC
Parallelism
72/100
Blocked
59%
Avg conflicts / tx
1.06
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #90,602,931 · 18 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
1w02w13w24w36w07w18w19w210w311w413w216w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5af098c7…4806
0x34b655…2a6f
6 touches
3 conflicts
0x95c47f03…f1bb
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x21898044…a071
0x065c9d…c394
6 touches
3 conflicts
0x51041fa9…df27
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…001e
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002e
0x1b6862…e19c
4 touches
1 conflict
0xba5743c7…21c5
0x1b6862…e19c
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 0x5af098c77e…e94806
Audit this contract →
← previous block·next block →recent activity