← previous blocknext block →recent activity
Analyzing
Block #90,040,906
16 transactions · 16 stateful · 2026-07-24 22:52:21 UTC
Parallelism
81/100
Blocked
31%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,040,906 · 16 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w26w08w110w112w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0xa4dae615…1cf8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x80a745fc…ce9e
0x851145…3f07
4 touches
1 conflict
0x909def91…71d2
0x851145…3f07
4 touches
1 conflict
0x6ed7783a…f404
0x851145…3f07
4 touches
1 conflict
0x8cf3d245…1d0d
0x2b46c0…1669
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: Kuru Exchange: MarginAccount
3 conflicts on slot 0x889d5e90c7…59929a
Audit this contract →
← previous block·next block →recent activity