pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,195,631
← previous block
next block →
recent activity
Analyzing
Block #94,195,631
10 transactions · 9 stateful · 2026-08-08 11:38:59 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,195,631
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
0xab083028
#3
0x5acec890
#4
0x3f5c179b
#5
placeAndExecuteMarketBuy
#6
execFwdPositionOps
#7
execFwdPositionOps
· blocks 1
#9
updateDataFeedsValuesPartial
#8
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf4db760d…fc5b
0x34b655…2a6f
4 touches
1 conflict
0xf4db760d…fc5c
0x34b655…2a6f
4 touches
1 conflict
0x7141ca79…8cf9
0x34b655…2a6f
4 touches
1 conflict
0xc1c59e77…d053
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x0360769a…ad48
0x34b655…2a6f
4 touches
1 conflict
0xbc96083d…124d
0x34b655…2a6f
2 touches
0 conflicts
0xbca4de0c…577c
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
0xf4db760d0a…f0fc5b
Audit this contract →
← previous block
·
next block →
recent activity