← previous blocknext block →recent activity
Analyzing
Block #99,123,607
22 transactions · 21 stateful · 2026-08-25 19:15:15 UTC
Parallelism
73/100
Blocked
48%
Avg conflicts / tx
0.82
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #99,123,607 · 22 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w36w47w58w49w010w114w015w118w119w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x889d5e90…929a
0x2a68ba…90c5
10 touches
10 conflicts
0xb64473b0…0d6f
0xc8689a…ee79
6 touches
3 conflicts
0xf7640726…19a2
0x2a68ba…90c5
4 touches
1 conflict
0x08d53462…97ef
0x2b46c0…1669
4 touches
1 conflict
0x5a409e7f…09b6
0x2b46c0…1669
4 touches
1 conflict
0x7a12283f…b18a
0x2b46c0…1669
4 touches
1 conflict
0x8b2c44b4…7e59
0x2b46c0…1669
4 touches
1 conflict
0x915c095e…c1e5
0x2b46c0…1669
4 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
10 conflicts on slot 0x889d5e90c7…59929a
Audit this contract →
← previous block·next block →recent activity