pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,248,300
← previous block
next block →
recent activity
Analyzing
Block #93,248,300
10 transactions · 9 stateful · 2026-08-05 04:12:07 UTC
Parallelism
70
/100
Blocked
33
%
Avg conflicts / tx
0.3
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,248,300
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0xab083028
· blocks 1
#3
updateDataFeedsValuesPartial
#5
execFwdPositionOps
· blocks 1
#7
setData
#8
0x7d4cf2…649f
#9
setPrices
#2
0x6ad2e98b
· blocks 1
#6
execFwdPositionOps
#4
0x3f5c179b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
4
w2
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfc8cd993…5c11
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x1a3ca58e…6490
0x851145…3f07
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x6507044e…bcd6
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xcfe06a18…b5b5
0x2b46c0…1669
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
0xfc8cd99357…7e5c11
Audit this contract →
← previous block
·
next block →
recent activity