← previous blocknext block →recent activity
Analyzing
Block #95,796,560
10 transactions · 7 stateful · 2026-08-14 02:20:59 UTC
Parallelism
60/100
Blocked
43%
Avg conflicts / tx
0.6
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #95,796,560 · 10 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w27w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa1087a5c…66c4
0x754704…b603
8 touches
6 conflicts
0x456dc17f…da75
0x065c9d…c394
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0xa2478c84…6956
0x754704…b603
4 touches
1 conflict
0x1fca5190…99a7
0x065c9d…c394
4 touches
1 conflict
0x7e0b7922…c351
0x754704…b603
2 touches
0 conflicts
0x01a89030…f786
0x98dc6e…8633
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: USDC (USDC)
6 conflicts on slot 0xa1087a5ca6…0a66c4
Audit this contract →
← previous block·next block →recent activity