pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,683,605
← previous block
next block →
recent activity
Analyzing
Block #93,683,605
11 transactions · 8 stateful · 2026-08-06 16:40:35 UTC
Parallelism
73
/100
Blocked
25
%
Avg conflicts / tx
0.27
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,683,605
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
executePacked
#2
execOrder
· blocks 2
#3
execOrder
#4
0xbb1740dd
#7
0xed82b078
#8
updateDataFeedsValuesPartial
#9
setData
#10
0xc7e3ec2c
#5
execFwdPositionOps
· blocks 1
#6
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
5
w1
6
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x08e8f2c9…a11a
0x34b655…2a6f
4 touches
1 conflict
0xa9a9d0e0…4087
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x11258774…9892
0x2a68ba…90c5
2 touches
0 conflicts
0x4c4c97a5…70e5
0x34b655…2a6f
2 touches
0 conflicts
0x948836ff…59ab
0x34b655…2a6f
2 touches
0 conflicts
0x9c2fc330…0091
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:
Perpl
3 conflicts on slot
0x482471adbb…39122f
Audit this contract →
← previous block
·
next block →
recent activity