pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,522,187
← previous block
next block →
recent activity
Analyzing
Block #93,522,187
11 transactions · 10 stateful · 2026-08-06 03:09:07 UTC
Parallelism
82
/100
Blocked
10
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,522,187
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5acec890
· blocks 1
#2
execFwdPositionOps
#3
execFwdPositionOps
#4
updateDataFeedsValuesPartial
#5
updateDataFeedsValuesPartial
#6
placeAndExecuteMarketSell
#7
0x6a73fb4b
#8
setData
#10
0x59558d29
#9
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x08330b36…ae29
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x05b1b07a…7a99
0x34b655…2a6f
2 touches
0 conflicts
0x4a5956ef…e226
0x34b655…2a6f
2 touches
0 conflicts
0x56aee538…6f1f
0x34b655…2a6f
2 touches
0 conflicts
0x6bab0076…422b
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
0x08330b3687…a7ae29
Audit this contract →
← previous block
·
next block →
recent activity