← previous blocknext block →recent activity
Analyzing
Block #95,568,352
10 transactions · 9 stateful · 2026-08-13 07:12:07 UTC
Parallelism
80/100
Blocked
22%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #95,568,352 · 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
1w02w13w04w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdc255d21…c377
0x754704…b603
4 touches
1 conflict
0xe20cfb89…cd07
0x754704…b603
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0xaad1c5c0…ab91
0x754704…b603
4 touches
1 conflict
0x4dbb0f3e…2028
0x99c7a7…8bf0
4 touches
1 conflict
0xef712f4a…0853
0x99c7a7…8bf0
4 touches
1 conflict
0x7a12283f…b18a
0x2b46c0…1669
2 touches
0 conflicts
0x8b2c44b4…7e59
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: USDC (USDC)
1 conflict on slot 0xdc255d2170…b4c377
Audit this contract →
← previous block·next block →recent activity