← previous blocknext block →recent activity
Analyzing
Block #95,181,220
20 transactions · 18 stateful · 2026-08-11 22:31:21 UTC
Parallelism
60/100
Blocked
56%
Avg conflicts / tx
1.6
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #95,181,220 · 20 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w05w16w27w38w49w510w611w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2b54cadb…4425
0xd18b7e…414b
16 touches
28 conflicts
0xa1087a5c…66c4
0x754704…b603
16 touches
28 conflicts
0x49ca384c…e772
0x40c49f…2af0
10 touches
10 conflicts
0x6518075e…2b17
0x2a68ba…90c5
10 touches
10 conflicts
0x002fed35…79fa
0x2a68ba…90c5
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x78ae8c48…a433
0x40c49f…2af0
6 touches
3 conflicts
0xafb8e71e…9285
0x34b655…2a6f
4 touches
1 conflict
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: Coinbase Wrapped BTC (cbBTC)
28 conflicts on slot 0x2b54cadb82…7c4425
Audit this contract →
← previous block·next block →recent activity