← previous blocknext block →recent activity
Analyzing
Block #95,390,906
17 transactions · 14 stateful · 2026-08-12 16:18:40 UTC
Parallelism
88/100
Blocked
29%
Avg conflicts / tx
0.24
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #95,390,906 · 17 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
1w03w17w08w09w111w115w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd519f276…aa62
0x0555e3…2b9c
4 touches
1 conflict
0xc5a1b2fe…5369
0x34b655…2a6f
4 touches
1 conflict
0xc75d0753…497a
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0003
0xd2634e…53b1
4 touches
1 conflict
0x00000000…0012
0xd2634e…53b1
4 touches
1 conflict
0x00000000…001a
0xd2634e…53b1
4 touches
1 conflict
0x00000000…001b
0xd2634e…53b1
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: Wrapped BTC (WBTC)
1 conflict on slot 0xd519f2761a…7daa62
Audit this contract →
← previous block·next block →recent activity