pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#101,304,400
← previous block
next block →
recent activity
Analyzing
Block #101,304,400
10 transactions · 10 stateful · 2026-09-02 10:28:00 UTC
Parallelism
80
/100
Blocked
10
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#101,304,400
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xa96df62f
#2
matchOrders
#3
0x5acec890
#4
updateDataFeedsValuesPartial
#5
execFwdPositionOpsV2
#6
executeBatch
· blocks 1
#8
0x6a97faa7
#9
setData
#7
executeBatch
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf79df061…e005
0xe52b14…7230
4 touches
1 conflict
0xf2dc09c1…226f
0xe52b14…7230
3 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0005a38a…d41c
0x34b655…2a6f
2 touches
0 conflicts
0x024b482b…16b0
0x34b655…2a6f
2 touches
0 conflicts
0x2d02f869…1f83
0x34b655…2a6f
2 touches
0 conflicts
0x336486a4…20bd
0x34b655…2a6f
2 touches
0 conflicts
0x34c316ed…4f89
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:
0xe52b1424…bb7230
1 conflict on slot
0xf79df061c7…91e005
Audit this contract →
← previous block
·
next block →
recent activity