pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,388,818
← previous block
next block →
recent activity
Analyzing
Block #93,388,818
10 transactions · 9 stateful · 2026-08-05 15:58:38 UTC
Parallelism
70
/100
Blocked
22
%
Avg conflicts / tx
0.3
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,388,818
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
execFwdPositionOps
· blocks 2
#2
updateDataFeedsValuesPartial
#3
0x3f5c179b
#6
0xed82b078
#7
0x6a735e26
#8
setData
#9
0x59558d29
#4
execFwdPositionOps
· blocks 1
#5
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
4
w1
5
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfed09e59…a493
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x83f3d320…fb59
0x34b655…2a6f
4 touches
1 conflict
0x4984f7be…d515
0x34b655…2a6f
4 touches
1 conflict
0xdaf4f143…58d4
0x2a68ba…90c5
2 touches
0 conflicts
0x1ab4c88c…49f2
0x34b655…2a6f
2 touches
0 conflicts
0x1ab4c88c…49f3
0x34b655…2a6f
2 touches
0 conflicts
0x30b4fed0…901a
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
0xfed09e59c7…d6a493
Audit this contract →
← previous block
·
next block →
recent activity