← previous blocknext block →recent activity
Analyzing
Block #99,092,499
17 transactions · 14 stateful · 2026-08-25 16:38:37 UTC
Parallelism
88/100
Blocked
21%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #99,092,499 · 17 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w08w110w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0xb55f6c75…c2d2
0xa6afd3…d132
4 touches
1 conflict
0xce678ecc…743b
0xa6afd3…d132
4 touches
1 conflict
0xded216ce…191a
0xa6afd3…d132
4 touches
1 conflict
0x8905d15b…7759
0xa6afd3…d132
3 touches
1 conflict
0xdeabe9d0…0fcc
0xa6afd3…d132
3 touches
1 conflict
0x7a48b09c…7d72
0xd32edf…ff58
3 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: Kuru Exchange: MarginAccount
1 conflict on slot 0x889d5e90c7…59929a
Audit this contract →
← previous block·next block →recent activity