← previous blocknext block →recent activity
Analyzing
Block #99,113,747
7 transactions · 7 stateful · 2026-08-25 18:25:32 UTC
Parallelism
57/100
Blocked
29%
Avg conflicts / tx
0.43
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,113,747 · 7 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
2w04w15w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x18846715…77e9
0x065c9d…c394
4 touches
1 conflict
0x0fbc8e87…11d6
0x065c9d…c394
3 touches
1 conflict
0xdb90b0e4…617f
0x065c9d…c394
3 touches
1 conflict
0xa790d6ca…ad4f
0x065c9d…c394
3 touches
1 conflict
0x28e259b6…8e20
0x065c9d…c394
3 touches
1 conflict
0xc8525006…2b45
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 0x046a928e85…e50012
Audit this contract →
← previous block·next block →recent activity