pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,655,593
← previous block
next block →
recent activity
Analyzing
Block #98,655,593
11 transactions · 9 stateful · 2026-08-24 03:46:11 UTC
Parallelism
73
/100
Blocked
22
%
Avg conflicts / tx
0.27
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,655,593
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x6ad2e98b
#2
0x5acec890
· blocks 2
#4
execOrder
#5
0x59558d29
#7
updatePosition
#8
0x6a8bbefb
#9
setData
#10
execute
#3
execOrders
· blocks 1
#6
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
6
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x558a3fb1…0e36
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x12b8a1cd…8b3a
0x34b655…2a6f
2 touches
0 conflicts
0x16639814…fff4
0x34b655…2a6f
2 touches
0 conflicts
0x1f00a5b3…bf76
0x34b655…2a6f
2 touches
0 conflicts
0x1fcdf998…1e59
0x34b655…2a6f
2 touches
0 conflicts
0x3d36ef5d…17f0
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
3 conflicts on slot
0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block
·
next block →
recent activity