pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,126,756
← previous block
next block →
recent activity
Analyzing
Block #96,126,756
13 transactions · 12 stateful · 2026-08-15 06:02:19 UTC
Parallelism
85
/100
Blocked
8
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,126,756
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x325dd70c
· blocks 1
#2
0xab083028
#3
0x0c7abd22
#5
updateDataFeedsValuesPartial
#6
updateDataFeedsValuesPartial
#7
0x62be7533
#8
handleOps
#9
execFwdPositionOpsV2
#10
execFwdPositionOpsV2
#11
setData
#12
0x61d59c2d
#4
0xa9b28aa6
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0000
0x834d94…8555
4 touches
1 conflict
0x0ef74796…cd18
0x0a3323…0a3c
4 touches
1 conflict
0x00000000…0004
0x834d94…8555
4 touches
1 conflict
0x00000000…0005
0x834d94…8555
4 touches
1 conflict
0xa060b594…669d
0x754704…b603
4 touches
1 conflict
0x3378736d…32b0
0x834d94…8555
4 touches
1 conflict
0x3378736d…32b1
0x834d94…8555
4 touches
1 conflict
0x3378736d…32b2
0x834d94…8555
4 touches
1 conflict
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:
0x834d94a0…2e8555
1 conflict on slot
0x0000000000…000000
Audit this contract →
← previous block
·
next block →
recent activity