pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,862,264
← previous block
next block →
recent activity
Analyzing
Block #94,862,264
12 transactions · 12 stateful · 2026-08-10 19:46:14 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
#94,862,264
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6a7a2afe
#2
execOrders
#3
0x5acec890
#4
0x5acec890
#5
0x3f5c179b
#6
execFwdPositionOps
· blocks 1
#8
updateDataFeedsValuesPartial
#9
setData
#10
execOrders
#11
0x59558d29
#7
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0x1507536e…933f
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x146f0fd7…34d3
0x34b655…2a6f
2 touches
0 conflicts
0x16ef6aaa…6eb2
0x34b655…2a6f
2 touches
0 conflicts
0x216ffe66…1f94
0x34b655…2a6f
2 touches
0 conflicts
0x24e578ef…2049
0x34b655…2a6f
2 touches
0 conflicts
0x3542128c…f6c4
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
0xbcbf5d09a8…c68bac
Audit this contract →
← previous block
·
next block →
recent activity