pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,790,447
← previous block
next block →
recent activity
Analyzing
Block #94,790,447
9 transactions · 8 stateful · 2026-08-10 13:44:56 UTC
Parallelism
78
/100
Blocked
25
%
Avg conflicts / tx
0.22
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,790,447
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
#2
0x6a79d650
· blocks 1
#4
updatePrices
· blocks 1
#6
execFwdPositionOps
#7
updateDataFeedsValuesPartial
#8
setData
#3
0x6a79d650
#5
updatePrices
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x00000000…0002
0xeae24c…0be0
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x03aa8b26…118a
0x34b655…2a6f
2 touches
0 conflicts
0x07cbae0b…e7a2
0x34b655…2a6f
2 touches
0 conflicts
0x1d2d55e0…ef26
0x34b655…2a6f
2 touches
0 conflicts
0x22df5a0b…595c
0x34b655…2a6f
2 touches
0 conflicts
0x24ca1902…7a87
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:
0x681e908b…e1ae09
1 conflict on slot
0x0d622e34f9…000000
Audit this contract →
← previous block
·
next block →
recent activity