← previous blocknext block →recent activity
Analyzing
Block #99,196,103
14 transactions · 14 stateful · 2026-08-26 01:19:59 UTC
Parallelism
79/100
Blocked
14%
Avg conflicts / tx
0.14
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,196,103 · 14 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
1w02w13w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x348fda08…7e96
0x065c9d…c394
4 touches
1 conflict
0xbb97db90…4c93
0xc8689a…ee79
4 touches
1 conflict
0x6893387a…aabc
0x065c9d…c394
2 touches
0 conflicts
0x997ccc40…4dfd
0x3bd359…433a
2 touches
0 conflicts
0xe2745681…ff50
0x3bd359…433a
2 touches
0 conflicts
0x00000000…0000
0x52c17a…f6f4
2 touches
0 conflicts
0xde7e8c4d…5b05
0x52c17a…f6f4
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