← previous blocknext block →recent activity
Analyzing
Block #99,700,169
10 transactions · 10 stateful · 2026-08-27 19:45:44 UTC
Parallelism
80/100
Blocked
20%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #99,700,169 · 10 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
1w02w13w04w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x15c6ded9…48e7
0x754704…b603
4 touches
1 conflict
0x5a7e4e98…1f3b
0x754704…b603
4 touches
1 conflict
0xd4c946a4…b8d4
0x754704…b603
4 touches
1 conflict
0x45436af6…437f
0x99c7a7…8bf0
4 touches
1 conflict
0x66300207…c47a
0x99c7a7…8bf0
4 touches
1 conflict
0x53e50026…6d8c
0x2b46c0…1669
2 touches
0 conflicts
0x6eff310a…c34c
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
1 conflict on slot 0x889d5e90c7…59929a
Audit this contract →
← previous block·next block →recent activity