pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,932,609
← previous block
next block →
recent activity
Analyzing
Block #93,932,609
11 transactions · 10 stateful · 2026-08-07 13:32:51 UTC
Parallelism
73
/100
Blocked
20
%
Avg conflicts / tx
0.27
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,932,609
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x3d98fb1c
#2
execute
#3
execute
#4
execOrder
· blocks 2
#5
updateDataFeedsValuesPartial
#6
0xb2d4797b
#8
batchUpdate
#10
execOrders
#7
execFwdPositionOps
· blocks 1
#9
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
7
w1
9
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…000a
0x228589…f1ba
2 touches
0 conflicts
0x00000000…0000
0x2970fd…1fc2
2 touches
0 conflicts
0x0f12dea1…eed4
0x34b655…2a6f
2 touches
0 conflicts
0x00000000…0005
0x7821ba…01d0
2 touches
0 conflicts
0x00000000…0008
0x7821ba…01d0
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
3 conflicts on slot
0xc824469a90…af6425
Audit this contract →
← previous block
·
next block →
recent activity