pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,484,968
← previous block
next block →
recent activity
Analyzing
Block #93,484,968
10 transactions · 10 stateful · 2026-08-06 00:02:01 UTC
Parallelism
80
/100
Blocked
10
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,484,968
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
updateDataFeedsValuesPartial
#3
execute
#4
0x0f6795d9
· blocks 1
#6
placeAndExecuteMarketSell
#7
0x6a73cf70
#8
setData
#9
0x39435dac
#5
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x52b477bc…7ccf
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0a005879…de60
0x34b655…2a6f
2 touches
0 conflicts
0x0a8f8b9c…3046
0x34b655…2a6f
2 touches
0 conflicts
0x0ab1986a…4790
0x34b655…2a6f
2 touches
0 conflicts
0x0baf743f…8d8a
0x34b655…2a6f
2 touches
0 conflicts
0x0c82e363…09ce
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
0x52b477bcb8…5d7ccf
Audit this contract →
← previous block
·
next block →
recent activity