pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,926,676
← previous block
next block →
recent activity
Analyzing
Block #93,926,676
11 transactions · 11 stateful · 2026-08-07 13:03:02 UTC
Parallelism
64
/100
Blocked
27
%
Avg conflicts / tx
0.55
Longest chain
4
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,926,676
· 11 txs across 4 waves · depth 4
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
#0
syscallReward
#1
execFwdPositionOps
#2
updateDataFeedsValuesPartial
#3
executeBatch
#4
0x3f5c179b
#5
execFwdPositionOps
#6
0x6df9e92b
· blocks 3
#10
setData
#7
0x6df9e92b
· blocks 2
#8
0x6df9e92b
· blocks 1
#9
0x6df9e92b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
8
w2
9
w3
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x116e7d…d8f1
8 touches
6 conflicts
0x00000000…0003
0x116e7d…d8f1
8 touches
6 conflicts
0x00000000…0000
0x116e7d…d8f1
8 touches
6 conflicts
0x44ad89ba…cf83
0x350035…7777
8 touches
6 conflicts
0x692a4122…76b8
0x350035…7777
8 touches
6 conflicts
0xa472d565…9fe4
0x3bd359…433a
8 touches
6 conflicts
0xb7143610…adc4
0x3bd359…433a
8 touches
6 conflicts
0x09000000…0001
0x000000…1000
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:
0x116e7d07…d7d8f1
6 conflicts on slot
0x0000000000…000002
Audit this contract →
← previous block
·
next block →
recent activity