pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#100,731,139
← previous block
next block →
recent activity
Analyzing
Block #100,731,139
7 transactions · 7 stateful · 2026-08-31 10:23:22 UTC
Parallelism
71
/100
Blocked
14
%
Avg conflicts / tx
0.29
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#100,731,139
· 7 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
· blocks 1
#2
0x928e4afa
· blocks 1
#3
setData
#5
0x57368ddf
#6
0x6a955691
#4
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x831f75b4…945d
0x34b655…2a6f
4 touches
1 conflict
0x5a95f394…be66
0x34b655…2a6f
4 touches
1 conflict
0x2229f653…8c8b
0x34b655…2a6f
4 touches
1 conflict
0xfedb5dba…a1e7
0x34b655…2a6f
4 touches
1 conflict
0x31d88d27…7617
0x34b655…2a6f
2 touches
0 conflicts
0x3be13b22…e859
0x34b655…2a6f
2 touches
0 conflicts
0x55192654…91fe
0x34b655…2a6f
2 touches
0 conflicts
0x57d6356f…2786
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
0x831f75b4aa…17945d
Audit this contract →
← previous block
·
next block →
recent activity