pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#100,154,946
← previous block
next block →
recent activity
Analyzing
Block #100,154,946
11 transactions · 10 stateful · 2026-08-29 10:00:34 UTC
Parallelism
82
/100
Blocked
10
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#100,154,946
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
0x8263f5d9
#3
0x59558d29
#4
forward
#5
executeBatch
· blocks 1
#7
setData
#8
execFwdPositionOpsV2
#9
execFwdPositionOpsV2
#10
execOrders
#6
executeBatch
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8ffa3328…ce11
0xe52b14…7230
4 touches
1 conflict
0xf79df061…e005
0xe52b14…7230
4 touches
1 conflict
0x0d118c18…7e1b
0xe52b14…7230
3 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
2 touches
0 conflicts
0x2f74f175…9285
0x2b46c0…1669
2 touches
0 conflicts
0x2f74f175…9289
0x2b46c0…1669
2 touches
0 conflicts
0x53e50026…6d8c
0x2b46c0…1669
2 touches
0 conflicts
0xce1efe70…2ec8
0x2b46c0…1669
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:
0xe52b1424…bb7230
1 conflict on slot
0x8ffa332881…c9ce11
Audit this contract →
← previous block
·
next block →
recent activity