pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,834,911
← previous block
next block →
recent activity
Analyzing
Block #86,834,911
25 transactions · 20 stateful · 2026-07-10 12:04:13 UTC
Parallelism
80
/100
Blocked
45
%
Avg conflicts / tx
0.52
Longest chain
5
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,834,911
· 25 txs across 5 waves · depth 5
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
wave
w4
#0
syscallReward
#1
0x957d4ba0
· blocks 2
#4
0xab083028
· blocks 3
#5
0x5a5d9a99
· blocks 1
#6
0x5a5d9a99
#8
artefact_keep
#9
0x6a50e035
#11
execFwdPositionOps
#12
execFwdPositionOps
#13
updateDataFeedsValuesPartial
#14
cancel
#17
0x29eed2d3
#21
0x6a50e035
#22
setData
#23
0xe78882…c30f
#24
execOrders
#2
0x957d4ba0
· blocks 1
#7
0x5a5d9a99
· blocks 1
#15
0x3f5c179b
· blocks 2
#3
0x957d4ba0
#10
execFwdPositionOps
· blocks 1
#19
0xed82b078
· blocks 1
#16
execFwdPositionOps
· blocks 1
#20
0xed82b078
#18
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w2
4
w0
5
w0
7
w1
10
w2
15
w1
16
w3
18
w4
19
w2
20
w3
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0x93c58e4d…9b32
0x336ed4…c59c
6 touches
3 conflicts
0x085c9fac…8fcf
0x8d1565…6723
6 touches
3 conflicts
0x10a2bd5d…ad6d
0x8d1565…6723
6 touches
3 conflicts
0x00000000…000a
0x90c374…be45
6 touches
3 conflicts
0x00000000…000b
0x90c374…be45
6 touches
3 conflicts
0x7cfe59e0…2ec1
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
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:
Kuru Exchange: Market-WETH/USDC
6 conflicts on slot
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity