← previous blocknext block →recent activity
Analyzing
Block #95,473,893
10 transactions · 9 stateful · 2026-08-12 23:17:02 UTC
Parallelism
80/100
Blocked
11%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #95,473,893 · 10 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
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9b3dc479…55fb
0xa6afd3…d132
4 touches
1 conflict
0x11b69a7e…334e
0xee8c0e…1242
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0xd6bd849a…5597
0x2a68ba…90c5
4 touches
1 conflict
0x2a9e9bd1…5368
0x2a68ba…90c5
2 touches
0 conflicts
0x067bd7d7…fa42
0x34b655…2a6f
2 touches
0 conflicts
0x11416791…45e7
0x34b655…2a6f
2 touches
0 conflicts
0x4c1fbdf6…953d
0x754704…b603
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-WETH/USDC
1 conflict on slot 0x9b3dc47909…5d55fb
Audit this contract →
← previous block·next block →recent activity