← previous blocknext block →recent activity
Analyzing
Block #95,196,254
16 transactions · 16 stateful · 2026-08-11 23:46:58 UTC
Parallelism
81/100
Blocked
13%
Avg conflicts / tx
0.19
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #95,196,254 · 16 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
5w06w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x002fed35…79fa
0x2a68ba…90c5
4 touches
1 conflict
0x2b54cadb…4425
0xd18b7e…414b
4 touches
1 conflict
0x6518075e…2b17
0x2a68ba…90c5
4 touches
1 conflict
0xe46aa281…b7c8
0x40c49f…2af0
3 touches
1 conflict
0xce1cc6cd…1755
0x40c49f…2af0
3 touches
1 conflict
0x706c758c…2fdb
0x34b655…2a6f
2 touches
0 conflicts
0x730c8155…0856
0x34b655…2a6f
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 0xa1087a5ca6…0a66c4
Audit this contract →
← previous block·next block →recent activity