pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#100,705,545
← previous block
next block →
recent activity
Analyzing
Block #100,705,545
9 transactions · 9 stateful · 2026-08-31 08:14:36 UTC
Parallelism
78
/100
Blocked
11
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#100,705,545
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x8263f5d9
#2
execOrder
· blocks 1
#3
updateDataFeedsValuesPartial
#4
setData
#5
0x3f5c179b
#6
execFwdPositionOpsV2
#8
0x6a953864
#7
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x10d80fee…dbda
0x34ae4d…3fc5
2 touches
0 conflicts
0x1b9f9b78…a2b7
0x34ae4d…3fc5
2 touches
0 conflicts
0x7aa91b8f…d070
0x34ae4d…3fc5
2 touches
0 conflicts
0xe2263bea…6aa0
0x34ae4d…3fc5
2 touches
0 conflicts
0xe2263bea…6aa2
0x34ae4d…3fc5
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
0xc824469a90…af6425
Audit this contract →
← previous block
·
next block →
recent activity