pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#74,527,838
← previous block
next block →
recent activity
Analyzing
Block #74,527,838
11 transactions · 9 stateful · 2026-05-14 11:31:38 UTC
Parallelism
82
/100
Blocked
11
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,527,838
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x1ffa3c9b
#2
exactInputSingle
#3
updateDataFeedsValuesPartial
#4
updateTemporalNumericValuesV1
#5
0x6a05b312
#6
approve
#7
setData
#8
execOrders
· blocks 1
#10
multicall
#9
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa3ff1ab2…8ae3
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x085df2c1…305a
0x34b655…2a6f
4 touches
1 conflict
0x1952c598…df64
0x34b655…2a6f
4 touches
1 conflict
0x8d0e98f3…7ba0
0x34b655…2a6f
3 touches
1 conflict
0x8427451e…7622
0x065c9d…c394
2 touches
0 conflicts
0xa7477eac…c855
0x065c9d…c394
2 touches
0 conflicts
0xeb0fd275…2be9
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
0xa3ff1ab2e8…2a8ae3
Audit this contract →
← previous block
·
next block →
recent activity