← previous blocknext block →recent activity
Analyzing
Block #95,811,219
10 transactions · 10 stateful · 2026-08-14 03:34:43 UTC
Parallelism
70/100
Blocked
20%
Avg conflicts / tx
0.3
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #95,811,219 · 10 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
1w02w15w06w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x5a052fb6…2ace
0x065c9d…c394
4 touches
1 conflict
0x5ce0840a…f579
0x065c9d…c394
4 touches
1 conflict
0x6f29827f…a902
0x065c9d…c394
3 touches
1 conflict
0xc0f90b8d…401d
0x065c9d…c394
3 touches
1 conflict
0xdc91a7a2…81d6
0x065c9d…c394
3 touches
1 conflict
0xe2106324…821b
0x065c9d…c394
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