pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,878,722
← previous block
next block →
recent activity
Analyzing
Block #93,878,722
10 transactions · 8 stateful · 2026-08-07 09:01:29 UTC
Parallelism
70
/100
Blocked
25
%
Avg conflicts / tx
0.2
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,878,722
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
execOrders
#2
0x5acec890
· blocks 1
#3
updateDataFeedsValuesPartial
#5
execOrders
#7
0x6a759f61
#8
0xd708c5d8
#9
setData
#4
execFwdPositionOps
· blocks 1
#6
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
4
w1
6
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9ba6ae4a…90cb
0x34b655…2a6f
4 touches
1 conflict
0xb7d8840b…84ac
0x34b655…2a6f
4 touches
1 conflict
0x6713b018…05f3
0x34b655…2a6f
4 touches
1 conflict
0x282f129e…8f33
0x34b655…2a6f
2 touches
0 conflicts
0x4964acbd…62f4
0x34b655…2a6f
2 touches
0 conflicts
0x4bfdcd51…9b58
0x34b655…2a6f
2 touches
0 conflicts
0x51087f5a…61f7
0x34b655…2a6f
2 touches
0 conflicts
0x548b6abc…cb24
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
1 conflict on slot
0x9ba6ae4a28…c990cb
Audit this contract →
← previous block
·
next block →
recent activity