← previous blocknext block →recent activity
Analyzing
Block #96,696,395
8 transactions · 8 stateful · 2026-08-17 05:47:41 UTC
Parallelism
75/100
Blocked
25%
Avg conflicts / tx
0.25
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,696,395 · 8 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w16w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2886e2bc…6ab8
0x065c9d…c394
4 touches
1 conflict
0x6bdb9869…7558
0x34b655…2a6f
4 touches
1 conflict
0x1025416d…f8ba
0x065c9d…c394
3 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x92eaab4e…f5da
0x065c9d…c394
2 touches
0 conflicts
0x94719ebe…7ec9
0x065c9d…c394
2 touches
0 conflicts
0xb7ac0cea…edb3
0x065c9d…c394
2 touches
0 conflicts
0xd302594d…596e
0x065c9d…c394
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: Market-MON/USDC
1 conflict on slot 0x2886e2bc57…316ab8
Audit this contract →
← previous block·next block →recent activity