pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,287,740
← previous block
next block →
recent activity
Analyzing
Block #94,287,740
8 transactions · 8 stateful · 2026-08-08 19:25:43 UTC
Parallelism
75
/100
Blocked
25
%
Avg conflicts / tx
0.25
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,287,740
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
execFwdPositionOps
· blocks 2
#4
updateDataFeedsValuesPartial
#6
0x6a77832f
#7
setData
#3
execFwdPositionOps
#5
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6740e400…8fa5
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0x17abd0b1…f478
0x34b655…2a6f
4 touches
1 conflict
0x11cf39d9…a032
0x34b655…2a6f
2 touches
0 conflicts
0x21ef0807…d889
0x34b655…2a6f
2 touches
0 conflicts
0x31b39922…1e65
0x34b655…2a6f
2 touches
0 conflicts
0x31b39922…1e66
0x34b655…2a6f
2 touches
0 conflicts
0x3b8f4938…bec8
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
0x6740e4007c…708fa5
Audit this contract →
← previous block
·
next block →
recent activity