pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,472,436
← previous block
next block →
recent activity
Analyzing
Block #93,472,436
10 transactions · 10 stateful · 2026-08-05 22:59:01 UTC
Parallelism
70
/100
Blocked
30
%
Avg conflicts / tx
0.4
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,472,436
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
updatePrices
#2
execFwdPositionOps
· blocks 2
#4
placeAndExecuteMarketBuy
#5
0x57368ddf
#7
setData
#8
0x59558d29
· blocks 1
#3
execFwdPositionOps
· blocks 1
#9
0x59558d29
#6
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
6
w2
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x50dbe610…177f
0x34b655…2a6f
6 touches
3 conflicts
0x1bf8d2af…d140
0x34b655…2a6f
4 touches
1 conflict
0x378c030c…a8a4
0x34b655…2a6f
4 touches
1 conflict
0x378c030c…a8a5
0x34b655…2a6f
4 touches
1 conflict
0x37d710c8…45c1
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x78b52df8…344b
0x34b655…2a6f
4 touches
1 conflict
0x816205a5…4fd1
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
3 conflicts on slot
0x50dbe61059…f8177f
Audit this contract →
← previous block
·
next block →
recent activity