pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#100,787,751
← previous block
next block →
recent activity
Analyzing
Block #100,787,751
13 transactions · 11 stateful · 2026-08-31 15:08:18 UTC
Parallelism
85
/100
Blocked
9
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#100,787,751
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
#2
0x59558d29
#3
execOrders
#4
execOrders
#5
execFwdPositionOpsV2
· blocks 1
#6
execFwdPositionOpsV2
#7
0x3f5c179b
#8
0x3f5c179b
#9
0x3f5c179b
#10
setData
#11
0xc7068c7b
#12
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
12
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x382434ca…96b5
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x05ab500a…6177
0x34b655…2a6f
2 touches
0 conflicts
0x0a809ce1…7894
0x34b655…2a6f
2 touches
0 conflicts
0x1016a4dc…b792
0x34b655…2a6f
2 touches
0 conflicts
0x142168c5…0ae6
0x34b655…2a6f
2 touches
0 conflicts
0x16aa0e68…6755
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
0x382434ca57…4d96b5
Audit this contract →
← previous block
·
next block →
recent activity