pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,321,697
← previous block
next block →
recent activity
Analyzing
Block #93,321,697
7 transactions · 5 stateful · 2026-08-05 10:21:09 UTC
Parallelism
57
/100
Blocked
40
%
Avg conflicts / tx
0.43
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,321,697
· 7 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
execFwdPositionOps
· blocks 2
#4
updateDataFeedsValuesPartial
#5
0x6a730f0d
#6
setData
#2
execFwdPositionOps
· blocks 1
#3
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6f988a4a…b39f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6426
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xac3e4969…39e9
0x34b655…2a6f
4 touches
1 conflict
0xa3ed5a09…c6d3
0x34b655…2a6f
4 touches
1 conflict
0x9b6c3273…9421
0x34b655…2a6f
4 touches
1 conflict
0x90c6414a…4aec
0x34b655…2a6f
4 touches
1 conflict
0x7b6d2deb…dde0
0x34b655…2a6f
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:
Perpl
1 conflict on slot
0x6f988a4a25…f9b39f
Audit this contract →
← previous block
·
next block →
recent activity