pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,299,060
← previous block
next block →
recent activity
Analyzing
Block #94,299,060
8 transactions · 7 stateful · 2026-08-08 20:23:02 UTC
Parallelism
75
/100
Blocked
14
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,299,060
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrder
#2
updateDataFeedsValuesPartial
#3
updatePriceFeedsIfNecessary
#4
0x3f5c179b
#5
execFwdPositionOps
· blocks 1
#7
setData
#6
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1880a7cf…461a
0x34b655…2a6f
4 touches
1 conflict
0xf5b23754…5eb1
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x7c3d51a9…db36
0x34b655…2a6f
4 touches
1 conflict
0x7c3d51a9…db35
0x34b655…2a6f
4 touches
1 conflict
0x6561b826…f343
0x34b655…2a6f
4 touches
1 conflict
0xf6032c71…4cc6
0x34b655…2a6f
3 touches
1 conflict
0x33649c4f…b327
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
0x1880a7cf7b…0c461a
Audit this contract →
← previous block
·
next block →
recent activity