pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,390,095
← previous block
next block →
recent activity
Analyzing
Block #98,390,095
11 transactions · 11 stateful · 2026-08-23 05:01:36 UTC
Parallelism
82
/100
Blocked
9
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,390,095
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
#2
multicall
#3
0xab083028
#4
0x59558d29
#5
0x928e4afa
· blocks 1
#7
execFwdPositionOpsV2
#8
0x3f5c179b
#9
0x6a8a7f28
#10
setData
#6
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xad3e66be…dccc
0xc8689a…ee79
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0xf690d06e…5e46
0x34b655…2a6f
4 touches
1 conflict
0xfaefdbf4…bf65
0x34b655…2a6f
4 touches
1 conflict
0x4a5956ef…e226
0x34b655…2a6f
4 touches
1 conflict
0x575b33b3…4ac8
0x34b655…2a6f
4 touches
1 conflict
0x58620f29…db5a
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: Settlement / Helper
1 conflict on slot
0xad3e66bedd…10dccc
Audit this contract →
← previous block
·
next block →
recent activity