pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#100,982,458
← previous block
next block →
recent activity
Analyzing
Block #100,982,458
10 transactions · 9 stateful · 2026-09-01 07:27:58 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#100,982,458
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrder
#2
execOrders
#3
0x59558d29
#4
execPerpOps
· blocks 1
#6
execFwdPositionOpsV2
#7
transferWithAuthorization
#8
setData
#9
0x3f5c179b
#5
execPerpOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6ca15e14…7be8
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x08e8f2c9…a11a
0x34b655…2a6f
2 touches
0 conflicts
0x0ac8a40d…f11f
0x34b655…2a6f
2 touches
0 conflicts
0x1524a821…c579
0x34b655…2a6f
2 touches
0 conflicts
0x2162a7c5…937e
0x34b655…2a6f
2 touches
0 conflicts
0x2162a7c5…937f
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
0x6ca15e14f4…917be8
Audit this contract →
← previous block
·
next block →
recent activity