pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#100,583,357
← previous block
next block →
recent activity
Analyzing
Block #100,583,357
10 transactions · 8 stateful · 2026-08-30 21:59:58 UTC
Parallelism
80
/100
Blocked
13
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#100,583,357
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
forward
#2
0x59558d29
#3
execOrders
#4
execOrders
#5
execFwdPositionOpsV2
#6
0x3f5c179b
· blocks 1
#7
execFwdPositionOpsV2
#8
setData
#9
0xc7068c7b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x31762a87…3704
0x851145…3f07
4 touches
1 conflict
0x90b1f042…5833
0x851145…3f07
4 touches
1 conflict
0xf52df78b…16a0
0x851145…3f07
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
2 touches
0 conflicts
0x53f7214d…8ec6
0x34b655…2a6f
2 touches
0 conflicts
0x76c4467d…ce28
0x34b655…2a6f
2 touches
0 conflicts
0x7e5ea60a…c4aa
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:
0x851145ea…9f3f07
1 conflict on slot
0x31762a8711…c83704
Audit this contract →
← previous block
·
next block →
recent activity