pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,114,553
← previous block
next block →
recent activity
Analyzing
Block #90,114,553
11 transactions · 8 stateful · 2026-07-25 05:06:11 UTC
Parallelism
82
/100
Blocked
13
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,114,553
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
updateDataFeedsValuesPartial
#3
updateDataFeedsValuesPartial
#4
0x3f5c179b
#5
execFwdPositionOps
#6
execFwdPositionOps
#7
execOrders
#8
setData
#9
execOrders
· blocks 1
#10
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
9
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x05c3bda4…de90
0x34b655…2a6f
4 touches
1 conflict
0x0bd95eb4…e562
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xffac0f80…5cc3
0x34b655…2a6f
4 touches
1 conflict
0x21898044…a071
0x065c9d…c394
2 touches
0 conflicts
0x45ba1fcc…8084
0x065c9d…c394
2 touches
0 conflicts
0x58762d07…81c6
0x065c9d…c394
2 touches
0 conflicts
0x80afd9d9…57cf
0x065c9d…c394
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
0x05c3bda4e9…47de90
Audit this contract →
← previous block
·
next block →
recent activity