pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#89,840,949
← previous block
next block →
recent activity
Analyzing
Block #89,840,949
11 transactions · 11 stateful · 2026-07-24 06:05:46 UTC
Parallelism
82
/100
Blocked
18
%
Avg conflicts / tx
0.27
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#89,840,949
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
0x5a5d9a99
· blocks 2
#3
0x5a5d9a99
#4
updateDataFeedsValuesPartial
#5
execFwdPositionOps
· blocks 1
#6
0x3f5c179b
#7
0x57368ddf
#9
setData
#8
execOrders
#10
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
5
w0
8
w1
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x923c57f1…7810
0x34b655…2a6f
4 touches
1 conflict
0xc516fef7…841c
0x34b655…2a6f
4 touches
1 conflict
0x55cf4758…265c
0x34b655…2a6f
4 touches
1 conflict
0x6612841b…ee74
0x34b655…2a6f
4 touches
1 conflict
0x427f51fd…bd80
0x34b655…2a6f
4 touches
1 conflict
0xd7cf4f1d…ede0
0x34b655…2a6f
3 touches
1 conflict
0x427b538b…124f
0x34b655…2a6f
3 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:
Perpl
1 conflict on slot
0x6fe7d366be…a578ff
Audit this contract →
← previous block
·
next block →
recent activity