pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,072,919
← previous block
next block →
recent activity
Analyzing
Block #92,072,919
12 transactions · 12 stateful · 2026-08-01 01:37:41 UTC
Parallelism
83
/100
Blocked
17
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,072,919
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x39ecce49
· blocks 1
#3
0xab083028
· blocks 1
#4
updatePrices
#5
updateDataFeedsValuesPartial
#7
0x57368ddf
#8
execFwdPositionOps
#9
execFwdPositionOps
#10
setData
#11
0x59558d29
#2
0x39ecce49
#6
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdd43be87…f667
0xe1c8b7…3022
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x44ed742f…63f5
0x3bd359…433a
4 touches
1 conflict
0x4eb758b8…b13b
0x3bd359…433a
4 touches
1 conflict
0xc6101b5d…4361
0x3bd359…433a
4 touches
1 conflict
0x5504f74a…6874
0x43cf54…7777
4 touches
1 conflict
0x00000000…0004
0x48c3bb…b17b
4 touches
1 conflict
0xa164d951…1534
0xe1c8b7…3022
4 touches
1 conflict
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:
0xe1c8b733…e33022
1 conflict on slot
0xdd43be87b3…92f667
Audit this contract →
← previous block
·
next block →
recent activity