pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#102,446,337
← previous block
next block →
recent activity
Analyzing
Block #102,446,337
13 transactions · 13 stateful · 2026-09-06 10:33:36 UTC
Parallelism
85
/100
Blocked
15
%
Avg conflicts / tx
0.15
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#102,446,337
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0065144b
· blocks 1
#2
0xab083028
· blocks 1
#4
0xab083028
#5
updateDataFeedsValuesPartial
#6
execOrders
#7
0x0c7abd22
#8
setData
#10
execFwdPositionOpsV2
#11
postStateList
#12
0x6a9d4183
#3
0xab083028
#9
0x62be7533
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w0
3
w1
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0000
0x4b6ce4…7f37
4 touches
1 conflict
0x00000000…0001
0x4b6ce4…7f37
4 touches
1 conflict
0x00000000…0003
0x4b6ce4…7f37
4 touches
1 conflict
0x6f845aff…9fc9
0x3bd359…433a
4 touches
1 conflict
0x062b2598…4e28
0x43cf54…7777
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x2f74f175…9286
0x34ae4d…3fc5
2 touches
0 conflicts
0x2f74f175…9287
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:
0x4b6ce40b…657f37
1 conflict on slot
0x0000000000…000000
Audit this contract →
← previous block
·
next block →
recent activity