pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#91,543,192
← previous block
next block →
recent activity
Analyzing
Block #91,543,192
11 transactions · 9 stateful · 2026-07-30 05:12:57 UTC
Parallelism
82
/100
Blocked
22
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#91,543,192
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5a5d9a99
#2
execFwdPositionOps
· blocks 2
#4
updateDataFeedsValuesPartial
#5
0x57368ddf
#7
0x6a6addd1
#8
execOrders
#9
setData
#10
0x59558d29
#3
execFwdPositionOps
#6
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x03aa8b26…118a
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x01a08f7d…dec6
0x34b655…2a6f
2 touches
0 conflicts
0x06c42b66…3b09
0x34b655…2a6f
2 touches
0 conflicts
0x09b28069…e220
0x34b655…2a6f
2 touches
0 conflicts
0x166dfabc…b65f
0x34b655…2a6f
2 touches
0 conflicts
0x19795ad6…4a16
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
0xc824469a90…af6425
Audit this contract →
← previous block
·
next block →
recent activity