← previous blocknext block →recent activity
Analyzing
Block #99,090,665
39 transactions · 31 stateful · 2026-08-25 16:29:22 UTC
Parallelism
80/100
Blocked
55%
Avg conflicts / tx
1.18
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #99,090,665 · 39 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w15w16w27w39w410w512w630w535w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x889d5e90…929a
0x2a68ba…90c5
16 touches
28 conflicts
0xd08db6ee…a943
0x40c49f…2af0
8 touches
6 conflicts
0x00000000…003d
0x40c49f…2af0
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0x87d81a7a…ab8c
0xd32edf…ff58
5 touches
3 conflicts
0xfaad4c03…00ac
0x065c9d…c394
5 touches
3 conflicts
0x183b0da1…e182
0x40c49f…2af0
4 touches
2 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
28 conflicts on slot 0x889d5e90c7…59929a
Audit this contract →
← previous block·next block →recent activity