pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,181,114
← previous block
next block →
recent activity
Analyzing
Block #95,181,114
9 transactions · 8 stateful · 2026-08-11 22:30:49 UTC
Parallelism
78
/100
Blocked
25
%
Avg conflicts / tx
0.22
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,181,114
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
#2
0x5acec890
· blocks 1
#4
placeAndExecuteMarketSell
· blocks 1
#6
updateDataFeedsValuesPartial
#7
transfer
#8
setData
#3
execFwdPositionOps
#5
placeAndExecuteMarketBuy
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0caa5e3f…ea20
0x34b655…2a6f
4 touches
1 conflict
0xbc66586e…20fe
0x34b655…2a6f
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x2b54cadb…4425
0xd18b7e…414b
4 touches
1 conflict
0x201986e4…c48c
0x34b655…2a6f
2 touches
0 conflicts
0x23a85fab…daaf
0x34b655…2a6f
2 touches
0 conflicts
0x3d4a4a17…e015
0x34b655…2a6f
2 touches
0 conflicts
0x3e3f27ce…580c
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
0x0caa5e3f90…fcea20
Audit this contract →
← previous block
·
next block →
recent activity