← previous blocknext block →recent activity
Analyzing
Block #95,567,861
14 transactions · 13 stateful · 2026-08-13 07:09:39 UTC
Parallelism
86/100
Blocked
31%
Avg conflicts / tx
0.29
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #95,567,861 · 14 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
1w02w14w08w09w110w111w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf6bcda4b…88cd
0x968279…9342
4 touches
1 conflict
0xf6bcda4b…88ce
0x968279…9342
4 touches
1 conflict
0xf6bcda4b…88d1
0x968279…9342
4 touches
1 conflict
0xf6bcda4b…88d2
0x968279…9342
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0xe9452241…95a3
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: 0x96827978…f09342
1 conflict on slot 0xf6bcda4b45…5388cd
Audit this contract →
← previous block·next block →recent activity