pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,397,161
← previous block
next block →
recent activity
Analyzing
Block #95,397,161
11 transactions · 8 stateful · 2026-08-12 16:50:16 UTC
Parallelism
82
/100
Blocked
13
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,397,161
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xd00c54…cee1
#2
execOrder
#3
execFwdPositionOps
· blocks 1
#5
updateDataFeedsValuesPartial
#6
0x3f5c179b
#7
execOrders
#8
0x6a7ca4c0
#9
setData
#10
0x59558d29
#4
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1fbe7937…dc8f
0x34b655…2a6f
4 touches
1 conflict
0x9b2d3bee…8eeb
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…641f
0x34b655…2a6f
4 touches
1 conflict
0x42b10c57…3ee7
0x34b655…2a6f
4 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0xd392f9dc…0ae2
0x34b655…2a6f
3 touches
1 conflict
0x2d8487d0…24c6
0x34b655…2a6f
2 touches
0 conflicts
0x2fa1def8…bce5
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
0x1fbe793745…dfdc8f
Audit this contract →
← previous block
·
next block →
recent activity