pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,271,790
← previous block
next block →
recent activity
Analyzing
Block #98,271,790
10 transactions · 10 stateful · 2026-08-22 19:06:23 UTC
Parallelism
70
/100
Blocked
20
%
Avg conflicts / tx
0.3
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,271,790
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
execOrders
#2
0x59558d29
#3
0x5acec890
· blocks 2
#6
swap
#7
execFwdPositionOpsV2
#8
setData
#9
execOrders
#4
0x928e4afa
· blocks 1
#5
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
5
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x05b1b07a…7a99
0x34b655…2a6f
4 touches
1 conflict
0x0ea82d2c…c412
0x34b655…2a6f
4 touches
1 conflict
0x0eedaad7…d836
0x34b655…2a6f
4 touches
1 conflict
0x11db128b…1153
0x34b655…2a6f
4 touches
1 conflict
0x152a2f3e…13f8
0x34b655…2a6f
4 touches
1 conflict
0xad3e66be…dccc
0xc8689a…ee79
4 touches
1 conflict
0x9ae859db…2d84
0x34b655…2a6f
4 touches
1 conflict
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
0xca841faae5…71486a
Audit this contract →
← previous block
·
next block →
recent activity