pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,997,992
← previous block
next block →
recent activity
Analyzing
Block #90,997,992
13 transactions · 12 stateful · 2026-07-28 07:27:18 UTC
Parallelism
85
/100
Blocked
17
%
Avg conflicts / tx
0.23
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,997,992
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6c05cd2b
· blocks 1
#2
0x5a5d9a99
· blocks 1
#3
updateDataFeedsValuesPartial
#4
execFwdPositionOps
#5
0x3f5c179b
#6
executeBatch
#7
execFwdPositionOps
· blocks 1
#8
0xed82b078
#11
setData
#12
execOrders
#9
execOrders
#10
createModule
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w0
7
w0
9
w1
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0004
0xd5b70d…615b
4 touches
1 conflict
0x18aed20c…48f3
0x000000…012a
4 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x7c403af1…31b1
0x3bd359…433a
4 touches
1 conflict
0x00000000…0000
0xd5b70d…615b
4 touches
1 conflict
0x00000000…0003
0xd5b70d…615b
4 touches
1 conflict
0x00000000…0008
0x32ce1b…2174
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:
0xd5b70d70…f4615b
1 conflict on slot
0x0000000000…000004
Audit this contract →
← previous block
·
next block →
recent activity