pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,656,542
← previous block
next block →
recent activity
Analyzing
Block #93,656,542
12 transactions · 9 stateful · 2026-08-06 14:24:31 UTC
Parallelism
83
/100
Blocked
11
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,656,542
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
0x0c7abd22
#3
0xcbbdb31a
#4
0x5acec890
· blocks 1
#5
0x5acec890
#6
updateDataFeedsValuesPartial
#7
0x3f5c179b
#8
execFwdPositionOps
#9
forward
#10
setData
#11
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7da6eb60…b34e
0x34b655…2a6f
4 touches
1 conflict
0xd79e9cac…9f72
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x01a08f7d…dec6
0x34b655…2a6f
2 touches
0 conflicts
0x04b1c5e4…6f7b
0x34b655…2a6f
2 touches
0 conflicts
0x1f00a5b3…bf76
0x34b655…2a6f
2 touches
0 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
2 touches
0 conflicts
0x566330e2…ba04
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
0x7da6eb601b…b3b34e
Audit this contract →
← previous block
·
next block →
recent activity