pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#100,048,052
← previous block
next block →
recent activity
Analyzing
Block #100,048,052
11 transactions · 10 stateful · 2026-08-29 01:02:16 UTC
Parallelism
82
/100
Blocked
20
%
Avg conflicts / tx
0.27
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#100,048,052
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
0xab083028
#3
execOrders
· blocks 1
#4
0x59558d29
#5
setData
#6
execFwdPositionOpsV2
· blocks 1
#7
execFwdPositionOpsV2
· blocks 1
#9
0x6a923010
#8
execFwdPositionOpsV2
#10
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
6
w0
7
w0
8
w1
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd5982776…4847
0x34b655…2a6f
4 touches
1 conflict
0x2f835a56…0ded
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0x15698ac9…2a46
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x5890dedf…54c9
0x34b655…2a6f
2 touches
0 conflicts
0x65bdc5fa…d7f3
0x34b655…2a6f
2 touches
0 conflicts
0x826c0d98…b92f
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
0xd5982776a0…554847
Audit this contract →
← previous block
·
next block →
recent activity