pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#89,753,480
← previous block
next block →
recent activity
Analyzing
Block #89,753,480
13 transactions · 9 stateful · 2026-07-23 22:44:18 UTC
Parallelism
85
/100
Blocked
11
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#89,753,480
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
dagSwapByOrderId
· blocks 1
#2
0x5a5d9a99
#3
0x380dc1…c55e
#5
0x000000b2
#6
setData
#7
execFwdPositionOps
#8
execFwdPositionOps
#9
forward
#10
0x6a6299b9
#11
0x61633731
#12
execOrders
#4
dagSwapByOrderId
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0000
0x834d94…8555
4 touches
1 conflict
0x00000000…0003
0x834d94…8555
4 touches
1 conflict
0x00000000…0004
0x834d94…8555
4 touches
1 conflict
0xa060b594…669d
0x754704…b603
4 touches
1 conflict
0x0ef74796…cd18
0x0a3323…0a3c
4 touches
1 conflict
0xb1632c2f…d991
0x0a3323…0a3c
2 touches
0 conflicts
0xe57fdf48…d3a9
0x0a3323…0a3c
2 touches
0 conflicts
0x038b9243…553d
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:
0x834d94a0…2e8555
1 conflict on slot
0x0000000000…000000
Audit this contract →
← previous block
·
next block →
recent activity