pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,348,236
← previous block
next block →
recent activity
Analyzing
Block #93,348,236
8 transactions · 5 stateful · 2026-08-05 12:34:34 UTC
Parallelism
75
/100
Blocked
20
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,348,236
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x928e4afa
· blocks 1
#2
updateDataFeedsValuesPartial
#3
updateDataFeedsValuesPartial
#5
0xed82b078
#6
exactInputSingle
#7
0x59558d29
#4
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa6389d47…9a28
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x5c0fc3ec…a209
0x34b655…2a6f
2 touches
0 conflicts
0x64098913…b17c
0x34b655…2a6f
2 touches
0 conflicts
0x68c07cb9…ae14
0x34b655…2a6f
2 touches
0 conflicts
0x84d74093…7808
0x34b655…2a6f
2 touches
0 conflicts
0x8b76e9f2…54ee
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
0xa6389d470d…f19a28
Audit this contract →
← previous block
·
next block →
recent activity