← previous blocknext block →recent activity
Analyzing
Block #90,204,602
12 transactions · 11 stateful · 2026-07-25 12:40:22 UTC
Parallelism
67/100
Blocked
36%
Avg conflicts / tx
0.58
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,204,602 · 12 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
1w02w13w24w37w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0x8eed7e30…c1ef
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0f69f34e…c78e
0x34b655…2a6f
2 touches
0 conflicts
0x28e5dbea…2f7f
0x34b655…2a6f
2 touches
0 conflicts
0x3eede796…d745
0x34b655…2a6f
2 touches
0 conflicts
0x445eb3ef…77f9
0x34b655…2a6f
2 touches
0 conflicts
0x5e47cbde…9659
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