pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,499,002
← previous block
next block →
recent activity
Analyzing
Block #93,499,002
9 transactions · 7 stateful · 2026-08-06 01:12:34 UTC
Parallelism
78
/100
Blocked
14
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,499,002
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrder
· blocks 1
#2
updateDataFeedsValuesPartial
#4
execFwdPositionOps
#5
0x3f5c179b
#6
placeAndExecuteMarketSell
#7
setData
#8
0x59558d29
#3
execFwdPositionOps
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
0x94bb14fe…8f47
0x34b655…2a6f
4 touches
1 conflict
0xd66696e0…0842
0x34b655…2a6f
4 touches
1 conflict
0x70a7b5d6…fe0e
0x34b655…2a6f
4 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
2 touches
0 conflicts
0x07bb3f5a…617e
0x34b655…2a6f
2 touches
0 conflicts
0x206f4379…e08a
0x34b655…2a6f
2 touches
0 conflicts
0x27099c8c…d9d5
0x34b655…2a6f
2 touches
0 conflicts
0x2e5ec52c…0fea
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
0x94bb14fe40…668f47
Audit this contract →
← previous block
·
next block →
recent activity