pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#100,109,928
← previous block
next block →
recent activity
Analyzing
Block #100,109,928
11 transactions · 11 stateful · 2026-08-29 06:13:47 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
#100,109,928
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
matchOrders
#2
execOrders
#3
0x5acec890
#4
0x5acec890
· blocks 1
#5
0x59558d29
#6
setData
#7
execFwdPositionOpsV2
#8
0xed82b078
#10
0x6a927912
#9
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xedee7e09…6888
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0476d77b…a514
0x34b655…2a6f
2 touches
0 conflicts
0x168405e7…f38d
0x34b655…2a6f
2 touches
0 conflicts
0x1b5d2e60…99b5
0x34b655…2a6f
2 touches
0 conflicts
0x1e168c8b…6945
0x34b655…2a6f
2 touches
0 conflicts
0x6ac4a9ce…5f63
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
0xedee7e090f…056888
Audit this contract →
← previous block
·
next block →
recent activity