pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,758,388
← previous block
next block →
recent activity
Analyzing
Block #92,758,388
13 transactions · 11 stateful · 2026-08-03 11:06:17 UTC
Parallelism
85
/100
Blocked
9
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,758,388
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xaf5e395a
· blocks 1
#2
0xab083028
#4
0x5acec890
#5
0x5acec890
#6
0x919502…84f7
#7
batchUpdate
#8
execFwdPositionOps
#9
updateDataFeedsValuesPartial
#10
0x6a7076a1
#11
setData
#12
0xc7e3ec2c
#3
0xb414539a
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0ed0980e…e3a8
0x065c9d…c394
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…0000
0x16d564…365f
2 touches
0 conflicts
0x3a921be0…779c
0x2a68ba…90c5
2 touches
0 conflicts
0x889d5e90…929a
0x2a68ba…90c5
2 touches
0 conflicts
0x51ca3051…0972
0x3bd359…433a
2 touches
0 conflicts
0xb5ed555a…386f
0x3bd359…433a
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:
Kuru Exchange: Market-MON/USDC
1 conflict on slot
0x0ed0980e23…2ce3a8
Audit this contract →
← previous block
·
next block →
recent activity