pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#99,484,806
← previous block
next block →
recent activity
Analyzing
Block #99,484,806
9 transactions · 8 stateful · 2026-08-27 01:33:15 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
#99,484,806
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
0x59558d29
#3
execFwdPositionOpsV2
· blocks 1
#5
execFwdPositionOpsV2
#6
0x6a8f9453
#7
setData
#8
0x785f5745
#4
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x3e6302c8…64f5
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xf081c170…f590
0x34b655…2a6f
4 touches
1 conflict
0x42522e76…2593
0x34b655…2a6f
2 touches
0 conflicts
0x543a1be7…ea1d
0x34b655…2a6f
2 touches
0 conflicts
0x60a536a6…ef7a
0x34b655…2a6f
2 touches
0 conflicts
0x6266e26a…96ee
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
0x482471adbb…39122f
Audit this contract →
← previous block
·
next block →
recent activity