pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,692,731
← previous block
next block →
recent activity
Analyzing
Block #92,692,731
8 transactions · 7 stateful · 2026-08-03 05:35:49 UTC
Parallelism
75
/100
Blocked
14
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,692,731
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrder
· blocks 1
#3
updateDataFeedsValuesPartial
#4
execFwdPositionOps
#5
execFwdPositionOps
#6
setData
#7
0xc7e3ec2c
#2
execOrder
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd66696e0…0842
0x34b655…2a6f
4 touches
1 conflict
0xb255781f…2ffb
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x361f4a1b…1f14
0x34b655…2a6f
2 touches
0 conflicts
0x4188cc5f…2d2e
0x34b655…2a6f
2 touches
0 conflicts
0x4e135144…4167
0x34b655…2a6f
2 touches
0 conflicts
0x67b966d6…9696
0x34b655…2a6f
2 touches
0 conflicts
0x7ef4ba09…2a25
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
0xd66696e0dc…230842
Audit this contract →
← previous block
·
next block →
recent activity