pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,244,634
← previous block
next block →
recent activity
Analyzing
Block #95,244,634
13 transactions · 12 stateful · 2026-08-12 03:50:55 UTC
Parallelism
85
/100
Blocked
8
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,244,634
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xa96df62f
#2
execute
#3
execFwdPositionOps
#4
execFwdPositionOps
#5
setData
· blocks 1
#7
execOrders
#8
execOrders
#9
execOrders
#10
execOrders
#11
execOrders
#12
execOrders
#6
setData
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdbadf6b0…43b2
0x33176b…e078
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x190585a8…a17c
0x34b655…2a6f
2 touches
0 conflicts
0x1b1b086a…4542
0x34b655…2a6f
2 touches
0 conflicts
0x31b39922…1e66
0x34b655…2a6f
2 touches
0 conflicts
0x3b9bb58c…e73a
0x34b655…2a6f
2 touches
0 conflicts
0x60d93ca8…f522
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:
0x33176be2…ede078
1 conflict on slot
0xdbadf6b093…d843b2
Audit this contract →
← previous block
·
next block →
recent activity