pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#75,270,264
← previous block
next block →
recent activity
Analyzing
Block #75,270,264
12 transactions · 10 stateful · 2026-05-17 22:13:00 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
#75,270,264
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x323fe4ce
#2
0x42bbae7a
#3
updatePriceFeedsIfNecessary
#4
forward
#5
0xed82b078
#6
updateDataFeedsValuesPartial
#7
0x6a0a3de4
#8
transfer
#9
setData
#10
execOrders
· blocks 1
#11
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
10
w0
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfbabb02d…af07
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x064b2183…071a
0xea1b8e…c5ec
2 touches
0 conflicts
0x09744403…b936
0xea1b8e…c5ec
2 touches
0 conflicts
0x1c1a981e…f3da
0xea1b8e…c5ec
2 touches
0 conflicts
0x263ef9eb…71ab
0xea1b8e…c5ec
2 touches
0 conflicts
0x3572bd92…dd29
0xea1b8e…c5ec
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
0xfbabb02d20…00af07
Audit this contract →
← previous block
·
next block →
recent activity