pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,368,000
← previous block
next block →
recent activity
Analyzing
Block #98,368,000
11 transactions · 10 stateful · 2026-08-23 03:10:26 UTC
Parallelism
82
/100
Blocked
20
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,368,000
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
matchOrders
#3
0x928e4afa
· blocks 1
#4
updatePosition
#5
0x3f5c179b
#6
execFwdPositionOpsV2
#7
0x6a8a651a
#8
setData
· blocks 1
#9
setData
#10
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
8
w0
9
w1
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5c1b956d…14d3
0x34b655…2a6f
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x11db128b…1153
0x34b655…2a6f
2 touches
0 conflicts
0x2df76ecf…ad3a
0x34b655…2a6f
2 touches
0 conflicts
0x4a5956ef…e226
0x34b655…2a6f
2 touches
0 conflicts
0x590c9b87…7818
0x34b655…2a6f
2 touches
0 conflicts
0x68c07cb9…ae14
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
0x5c1b956d4c…d014d3
Audit this contract →
← previous block
·
next block →
recent activity