pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#88,367,392
← previous block
next block →
recent activity
Analyzing
Block #88,367,392
11 transactions · 10 stateful · 2026-07-17 14:54:47 UTC
Parallelism
82
/100
Blocked
10
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#88,367,392
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5a5d9a99
#2
updateDataFeedsValuesPartial
#3
executeBatch
#4
0x1fe271b4
· blocks 1
#6
execFwdPositionOps
#7
commit
#8
setData
#9
execOrders
#10
0xc7e3ec2c
#5
0x1fe271b4
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3977aa55…9e02
0x0a2fbf…29b1
4 touches
1 conflict
0x3977aa55…9e05
0x0a2fbf…29b1
4 touches
1 conflict
0x9f4c50b4…9bfb
0x0a2fbf…29b1
4 touches
1 conflict
0x9f4c50b4…9bfc
0x0a2fbf…29b1
4 touches
1 conflict
0x00000000…0006
0x0a2fbf…29b1
4 touches
1 conflict
0x3977aa55…9e01
0x0a2fbf…29b1
4 touches
1 conflict
0x00000000…0005
0x370e2e…63b4
4 touches
1 conflict
0x1bff683e…7ecb
0x754704…b603
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:
0x0a2fbf2d…f729b1
1 conflict on slot
0x3977aa55b2…b99e02
Audit this contract →
← previous block
·
next block →
recent activity