pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,809,707
← previous block
next block →
recent activity
Analyzing
Block #94,809,707
12 transactions · 10 stateful · 2026-08-10 15:21:49 UTC
Parallelism
75
/100
Blocked
20
%
Avg conflicts / tx
0.25
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,809,707
· 12 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x5ffd18…3f90
#2
0xab083028
#3
updatePrices
#4
execute
#5
updatePosition
#6
execFwdPositionOps
· blocks 2
#7
0xed82b078
#8
execFwdPositionOps
#9
setData
#10
execOrders
· blocks 1
#11
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
10
w1
11
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x734ee320…caae
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x15ff1c21…be21
0x6657d1…8ccc
2 touches
0 conflicts
0x17225866…449f
0x6657d1…8ccc
2 touches
0 conflicts
0x18cfa916…3dc8
0x6657d1…8ccc
2 touches
0 conflicts
0x20e4d955…096a
0x6657d1…8ccc
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:
Perpl
1 conflict on slot
0xac2a02739b…81721b
Audit this contract →
← previous block
·
next block →
recent activity