pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,319,508
← previous block
next block →
recent activity
Analyzing
Block #94,319,508
9 transactions · 8 stateful · 2026-08-08 22:06:47 UTC
Parallelism
78
/100
Blocked
13
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,319,508
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x60e03462
#2
execOrder
· blocks 1
#3
updateDataFeedsValuesPartial
#4
execFwdPositionOps
#6
0x64480813
#7
setData
#8
0xc7e3ec2c
#5
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x37bef14c…a6d5
0x34b655…2a6f
4 touches
1 conflict
0x56a653f2…7434
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x159cff26…7665
0x34b655…2a6f
2 touches
0 conflicts
0x1683d146…5ec2
0x34b655…2a6f
2 touches
0 conflicts
0x1ade7ceb…e6b4
0x34b655…2a6f
2 touches
0 conflicts
0x1c7d8244…74a9
0x34b655…2a6f
2 touches
0 conflicts
0x1f90c45d…89c3
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
0x37bef14cb9…88a6d5
Audit this contract →
← previous block
·
next block →
recent activity