pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,573,914
← previous block
next block →
recent activity
Analyzing
Block #95,573,914
12 transactions · 11 stateful · 2026-08-13 07:40:06 UTC
Parallelism
83
/100
Blocked
9
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,573,914
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5acec890
#2
updateDataFeedsValuesPartial
#3
execFwdPositionOps
#4
execFwdPositionOps
#5
executeBatch
· blocks 1
#7
execFwdPositionOps
#8
execFwdPositionOps
#9
0x6a7d754d
#10
setData
#11
0x59558d29
#6
executeBatch
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
0xf79df061…e005
0xe52b14…7230
4 touches
1 conflict
0xc2552ad0…51c9
0xe52b14…7230
3 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x1b9ba1ac…3e50
0x34b655…2a6f
2 touches
0 conflicts
0x2697123c…8526
0x34b655…2a6f
2 touches
0 conflicts
0x2a949bb2…8769
0x34b655…2a6f
2 touches
0 conflicts
0x42acbf95…eec3
0x34b655…2a6f
2 touches
0 conflicts
0x57330c5d…9973
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:
0xe52b1424…bb7230
1 conflict on slot
0xf79df061c7…91e005
Audit this contract →
← previous block
·
next block →
recent activity