pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,135,449
← previous block
next block →
recent activity
Analyzing
Block #96,135,449
12 transactions · 8 stateful · 2026-08-15 06:46:05 UTC
Parallelism
83
/100
Blocked
25
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,135,449
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#2
execute302
· blocks 1
#4
0xab083028
#5
updateDataFeedsValuesPartial
#6
updateDataFeedsValuesPartial
#7
createModule
#9
execFwdPositionOpsV2
#10
setData
#11
execute
#3
execute302
#8
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w0
3
w1
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x52c63247…ce02
0x0a3323…0a3c
4 touches
1 conflict
0xabe82eb6…a188
0xd32edf…ff58
3 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…0000
0x04ddf6…7f33
2 touches
0 conflicts
0x00000000…0002
0x04ddf6…7f33
2 touches
0 conflicts
0x00000000…0003
0x04ddf6…7f33
2 touches
0 conflicts
0x00000000…000a
0x04ddf6…7f33
2 touches
0 conflicts
0x39770227…6a2f
0x0a3323…0a3c
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:
0x0a332311…6e0a3c
1 conflict on slot
0x52c63247e1…bace02
Audit this contract →
← previous block
·
next block →
recent activity