pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,880,086
← previous block
next block →
recent activity
Analyzing
Block #93,880,086
9 transactions · 6 stateful · 2026-08-07 09:08:20 UTC
Parallelism
78
/100
Blocked
17
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,880,086
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execPerpOps
#2
execPerpOps
#3
updateDataFeedsValuesPartial
#4
execFwdPositionOps
· blocks 1
#6
executeBatch
#7
0x6a75a0fc
#8
setData
#5
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x361f4a1b…1f14
0x34b655…2a6f
4 touches
1 conflict
0xf454cca7…095a
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x06d13840…23a1
0x34b655…2a6f
2 touches
0 conflicts
0x088adada…2aa2
0x34b655…2a6f
2 touches
0 conflicts
0x17d94c79…2463
0x34b655…2a6f
2 touches
0 conflicts
0x2aab0897…78f7
0x34b655…2a6f
2 touches
0 conflicts
0x31b39922…1e66
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
0x361f4a1bf9…2d1f14
Audit this contract →
← previous block
·
next block →
recent activity