pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#100,586,234
← previous block
next block →
recent activity
Analyzing
Block #100,586,234
14 transactions · 11 stateful · 2026-08-30 22:14:26 UTC
Parallelism
86
/100
Blocked
18
%
Avg conflicts / tx
0.14
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#100,586,234
· 14 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
0xab083028
#3
0x59558d29
· blocks 1
#5
exec
#6
execFwdPositionOpsV2
· blocks 1
#8
setData
#9
forward
#10
execFwdPositionOpsV2
#11
transfer
#12
transfer
#13
execOrders
#4
0x59558d29
#7
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x10ca7c55…c28d
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x2fdfa032…139c
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x00000000…004b
0x80c745…7210
4 touches
1 conflict
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0x7fe97198…79ab
0x34b655…2a6f
4 touches
1 conflict
0xd6c976a1…1d47
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
1 conflict on slot
0x10ca7c5575…84c28d
Audit this contract →
← previous block
·
next block →
recent activity