pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,188,344
← previous block
next block →
recent activity
Analyzing
Block #92,188,344
12 transactions · 12 stateful · 2026-08-01 11:18:11 UTC
Parallelism
83
/100
Blocked
8
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,188,344
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6ad2e98b
#2
0x5acec890
#3
execFwdPositionOps
· blocks 1
#4
execFwdPositionOps
#5
updateDataFeedsValuesPartial
#6
0x0c7abd22
#8
0x57368ddf
#9
execOrders
#10
setData
#11
0x59558d29
#7
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf85fbefc…6825
0x34b655…2a6f
4 touches
1 conflict
0xc3412055…65de
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6426
0x34b655…2a6f
4 touches
1 conflict
0xcf17589f…048c
0x34b655…2a6f
4 touches
1 conflict
0xcf79910a…34db
0x34b655…2a6f
4 touches
1 conflict
0x09a90ed3…6897
0x34b655…2a6f
4 touches
1 conflict
0x226ae29a…2612
0x34b655…2a6f
4 touches
1 conflict
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
0xf85fbefc8f…bd6825
Audit this contract →
← previous block
·
next block →
recent activity