← previous blocknext block →recent activity
Analyzing
Block #95,371,436
16 transactions · 16 stateful · 2026-08-12 14:40:04 UTC
Parallelism
63/100
Blocked
44%
Avg conflicts / tx
0.69
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #95,371,436 · 16 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w36w49w510w011w115w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x116e7d…d8f1
6 touches
3 conflicts
0x5a1cd68f…4125
0x754704…b603
6 touches
3 conflicts
0x00000000…0003
0x116e7d…d8f1
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0x00000000…0000
0x116e7d…d8f1
6 touches
3 conflicts
0x692a4122…76b8
0x350035…7777
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0xb7143610…adc4
0x3bd359…433a
6 touches
3 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: 0x116e7d07…d7d8f1
3 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity