pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,052,186
← previous block
next block →
recent activity
Analyzing
Block #94,052,186
10 transactions · 9 stateful · 2026-08-07 23:34:22 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,052,186
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
placeAndExecuteMarketSell
#2
0x0f6795d9
· blocks 1
#4
0x0f6795d9
#5
updateDataFeedsValuesPartial
#6
updateDataFeedsValuesPartial
#7
0x6a766bf6
#8
setData
#9
0xc7e3ec2c
#3
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x2a9e9bd1…5368
0x2a68ba…90c5
2 touches
0 conflicts
0x0d759c8b…b9b2
0x34b655…2a6f
2 touches
0 conflicts
0x15be757a…275e
0x34b655…2a6f
2 touches
0 conflicts
0x15be757a…275f
0x34b655…2a6f
2 touches
0 conflicts
0x21b57095…2d15
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:
Perpl
1 conflict on slot
0xc824469a90…af6425
Audit this contract →
← previous block
·
next block →
recent activity