pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#100,440,239
← previous block
next block →
recent activity
Analyzing
Block #100,440,239
10 transactions · 7 stateful · 2026-08-30 09:59:54 UTC
Parallelism
80
/100
Blocked
14
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#100,440,239
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6ad2e98b
#2
execOrders
#3
execOrder
· blocks 1
#4
0x59558d29
#5
0x0c7abd22
#6
0x0c7abd22
#7
setData
#8
approve
#9
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2a965e25…fa30
0x34b655…2a6f
4 touches
1 conflict
0x758a0dd5…0f46
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x14b206bd…fd5e
0x34b655…2a6f
2 touches
0 conflicts
0x39479d9f…8985
0x34b655…2a6f
2 touches
0 conflicts
0x4be9812b…48a9
0x34b655…2a6f
2 touches
0 conflicts
0x5a548af5…0eb0
0x34b655…2a6f
2 touches
0 conflicts
0x6492fc54…95f1
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
0x2a965e25b6…46fa30
Audit this contract →
← previous block
·
next block →
recent activity