← previous blocknext block →recent activity
Analyzing
Block #96,708,755
13 transactions · 13 stateful · 2026-08-17 06:49:51 UTC
Parallelism
77/100
Blocked
23%
Avg conflicts / tx
0.31
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #96,708,755 · 13 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
1w06w07w18w212w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd6bd849a…5597
0x2a68ba…90c5
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x34731dbd…e467
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x734ee320…caae
0x34b655…2a6f
4 touches
1 conflict
0xcc351d6d…256b
0x34b655…2a6f
4 touches
1 conflict
0x55012d1a…3907
0x2b46c0…1669
2 touches
0 conflicts
0xb8fccd1b…b5f2
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 0xd6bd849ae7…7c5597
Audit this contract →
← previous block·next block →recent activity