pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,386,341
← previous block
next block →
recent activity
Analyzing
Block #90,386,341
12 transactions · 10 stateful · 2026-07-26 04:03:36 UTC
Parallelism
83
/100
Blocked
10
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,386,341
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
0x6ad2e98b
#3
0x5a5d9a99
#4
0x5a5d9a99
#5
updateDataFeedsValuesPartial
#6
execFwdPositionOps
· blocks 1
#7
execFwdPositionOps
#8
executeBatch
#10
proposeResolution
#11
setData
#9
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x172b0de5…980b
0x34b655…2a6f
4 touches
1 conflict
0x73503ce4…ceff
0x34b655…2a6f
4 touches
1 conflict
0xc13e1d5c…62c6
0x34b655…2a6f
4 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…641f
0x34b655…2a6f
4 touches
1 conflict
0xdab87f9b…3a80
0x34b655…2a6f
3 touches
1 conflict
0x9a287655…f785
0x34b655…2a6f
2 touches
0 conflicts
0xaedc3dd6…3c3b
0x34b655…2a6f
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:
Perpl
1 conflict on slot
0x172b0de5b2…14980b
Audit this contract →
← previous block
·
next block →
recent activity