pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#100,134,652
← previous block
next block →
recent activity
Analyzing
Block #100,134,652
11 transactions · 10 stateful · 2026-08-29 08:18:16 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
#100,134,652
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
0xab083028
#3
0x5acec890
· blocks 1
#4
0x59558d29
#5
0x59558d29
#6
setData
#8
execFwdPositionOpsV2
#9
execFwdPositionOpsV2
· blocks 1
#7
execFwdPositionOpsV2
#10
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
7
w1
9
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1e168c8b…6945
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x889d5e90…929a
0x2a68ba…90c5
2 touches
0 conflicts
0x62030a81…91be
0x34b655…2a6f
2 touches
0 conflicts
0x70ace55b…8c81
0x34b655…2a6f
2 touches
0 conflicts
0x7dae2392…57e5
0x34b655…2a6f
2 touches
0 conflicts
0x7e8c9a3e…f7ea
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
0x1e168c8bca…f56945
Audit this contract →
← previous block
·
next block →
recent activity